Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#30578 - [eina-svn] remove --enable-amalgamation

Attached to Project: Community Packages
Opened by Swift Geek (swiftgeek) - Saturday, 07 July 2012, 03:49 GMT
Last edited by Ronald van Haren (pressh) - Wednesday, 21 November 2012, 11:23 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Please remove --enable-amalgamation from this and any other e17 package
It's orphaned/obsolete and makes build useless for debugging
This task depends upon

Closed by  Ronald van Haren (pressh)
Wednesday, 21 November 2012, 11:23 GMT
Reason for closing:  None
Additional comments about closing:  svn packages are dropped (I also discussed amalgamation with upstream, it is fine to use if you don't need debugging info)
Comment by Swift Geek (swiftgeek) - Sunday, 08 July 2012, 00:38 GMT
Also don't strip if possible - e17's *-svn are full of bugs, so stripping wont help make a stable release ;)
Comment by Ronald van Haren (pressh) - Monday, 16 July 2012, 11:14 GMT
The packages are not meant for debugging. IMO you should use current svn checkouts if you want to do debugging, not snapshots that are some weeks old (or at least verify if you can reproduce it with a current checkout).

About the deprecation of amalgamation, do you have any source for this, I can't find it?

Comment by Swift Geek (swiftgeek) - Monday, 16 July 2012, 11:18 GMT
Join #e @freenode for latest info ;)
You could ask for this especially @raster (as i assume u need official confirmation of this)
Comment by Jelle van der Waa (jelly) - Tuesday, 31 July 2012, 09:29 GMT
ISn't the information stated somewhere in the svn log or bugtracker of e?
Comment by Alexander F. Rødseth (xyproto) - Monday, 27 August 2012, 13:02 GMT
Can't find any indication that amalgamation is deprecated anywhere online.
Here are the search results on trac.enlightenment.org: http://trac.enlightenment.org/e/search?q=amalgamation&noquickjump=1&blog=on&changeset=on&milestone=on&ticket=on&wiki=on
Comment by Swift Geek (swiftgeek) - Monday, 27 August 2012, 15:29 GMT
From my memory i can say amalgamation was doing something that gcc couldn't do in ancient times

And really use IRC -.- raster is a head (release-manager) of E17 project
Comment by Alexander F. Rødseth (xyproto) - Monday, 27 August 2012, 21:37 GMT
We're all on IRC, but looking for something more official. Is it expected that if anyone wonders about the rationale for deprecating it in the future, they have to ask on IRC too?
Comment by Swift Geek (swiftgeek) - Monday, 27 August 2012, 21:42 GMT
Nope
It was never intended to use in official package in the first place :]
The official way of packaging e17 is not using any enable/disable switches at all - if it doesn't work without them, then a bug report should be filled.
Comment by Alexander F. Rødseth (xyproto) - Monday, 27 August 2012, 22:02 GMT
I see. Thanks for making this clear. I agree that --enable-amalgamation should be removed, since it's not enabled by default (and since it's deprecated). Confirming the bug.
Comment by Ronald van Haren (pressh) - Tuesday, 28 August 2012, 04:46 GMT
If input switches are not to be used then why did they bother creating an official page indicating that some config switches are recommended?

Anyway I won't be back from holidays for another week so I can't check if these are default flags anyway. I will have a look at these config flags at some point when I have time but it is low on my priority list. I'll revisit this bug when I have time until then I won't change the flags.

Loading...