| Summary: | kdevelop - adding "debug" USE flag in ebuild | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sascha Herrmann <Sascha.Herrmann> |
| Component: | New packages | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | s041560 |
| Priority: | Highest | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Patch for adding debug flag | ||
|
Description
Sascha Herrmann
2004-02-22 11:23:47 UTC
Created attachment 26119 [details, diff]
Patch for adding debug flag
see above
ivalid, this is already done in kde eclass Okay, but this is VERY BAD documented. If you try "emerge -v kdevelop" no use of the debug flag is shown. So how should anybody know then??? maybe this should be implemented in portage??? Yes, Sascha, you're right. All the kde* eclasses are missing a
IUSE="${IUSE} foo bar"
line.
In fact it's only the kde.eclass which needs
IUSE="${IUSE} debug"
added.
added the IUSE in the kde.eclass. Caleb, that didn't do the trick: root@senote kde-base # emerge -pv kdevelop These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] dev-util/kdevelop-3.0.3 -doc +java +python -ruby 0 kB no debug USE flag... <snip from kde.eclass> ECLASS=kde INHERITED="$INHERITED $ECLASS" DESCRIPTION="Based on the $ECLASS eclass" HOMEPAGE="http://www.kde.org/" IUSE="${IUSE} debug" Looks like the IUSE have to go into the individual packages, or is kdevelop special? Also, shouldn't it use nostrip when making debug builds? also, can someone reopen this bug (if I'm not mistaking)? The debug use flag isn't shown, when declared in eclasses, but it works. This is a portage bug and fixed in the development version. what about the nostrip option? nostrip is not a use flag -> man make.conf Yes I know it's not a USE flag! But that doesn't change the fact that it should be applied for debug builds, or am I missing something??? Sorry for my slow mind. You're right of course. On the other hand Portage could be a bit smarter and do this by default, when the debug flag is set. Caleb: I think it would be better to drop the IUSE again and inherit the debug.eclass. Thank you very much!! Yes you are right...with less flags (-O2 -march=atholon-xp -pipe -fomit-frame-pointer) get compiled with no errors. Sorry for this post, the next time i will try before posting..;) Regards, ejuan what if we add a: use debug && FEATURE="$FEATURES nostrip" to the eclass? Caleb: If we do this then it should be RESTRICT="nostrip". FEATURES should never be modified. I put this bug aside because of Bug 55708, which is fixed now according to Nicholas. Just need to find out what exactly this means and if Portage adds nostrip by itself, now. I'm sorry - yes, I meant RESTRICT instead of FEATURES Did anyone understand what's the opinion of portage-devs on this topic? Don't know about the portage devs, but they haven't been telling people not to use debug.eclass, right? And (useq debug && RESTRICT=nostrip) is exactly what it does. So AFAICS we should just inherit debug from kde.eclass... Dan: Dynamic RESTRICT breaks caching. That's why debug should become a feature instead a use flag as described in Bug 55708. I just can't see that it is a valid feature now... Ah OK, sorry. |
