Summary: | New USER_ALLOWED_FLAGS variable | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kaiting Chen <Phoenixfire159> |
Component: | New packages | Assignee: | SpanKY <vapier> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kaiting Chen
2005-01-27 12:10:17 UTC
strip-flags is to produce a sane system if the user is allowed to control the idea of a 'sane system', bad things can (and do) happen Yeah, but that's the user's own fault. I mean, just because you implement this doesn't mean that everyone's going to use it. It's just annoying having to update the eclass every time I emerge --sync. If we could overlay eclasses, that would be great to. But as things stand, I don't think it would cause any problems for this to be implemented, and with a warning in /etc/make.conf.example such as: "This can and probably will break your system." And another thing. Fomit-frame-pointer rarely causes problems. In fact, I have my entire system compiled with that flag, (except for glibc and the like, which explicitly filter it out). Lots of ebuilds just call strip-flags just for the heck of it, which unfortunately, filters out fomit-frame-pointer. i dont care, it's not going to happen hrm, neglected to close the bug last time You can overlay eclasses, btw. |