| Summary: | colorgcc-1.3.2.ebuild violates CONFIG_PROTECT | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Tod M. Neidt <tneidt> |
| Component: | [OLD] Development | Assignee: | Daniel Robbins (RETIRED) <drobbins> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | esigra, g2boojum |
| Priority: | High | ||
| Version: | 1.0 RC6 r14 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
fixed on cvs. Thanks for your patience :) It looks like -r1 wasn't committed. committed now |
Hi! I gotten use to CONFIG_PROTECT not allowing changes to existing config files in /etc, so it bothers me when an ebuild does this. Using pkg_postinst to change /etc/profile is cheating :) options that I can think of: 1. Just echo the info to the screen in pkg_postinst telling the user to modify /etc/profile, or their .bashrc 2. Include a modified profile.colorgcc file in the colorgcc/files directory and then insinto /etc newins ${FILESDIR}/profile.colorgcc profile CONFIG_PROTECT will catch this and create a ._cfg0000_profile in /etc I like color! tod