| 1 |
Justin (jlec) posted on Fri, 20 Sep 2013 19:58:51 +0200 as excerpted: |
| 2 |
|
| 3 |
> what is your opinion to set |
| 4 |
> |
| 5 |
> FEATURES="binchecks strip" |
| 6 |
> |
| 7 |
> for all those packages which purely install files. For example python |
| 8 |
> package only installing scripts, or perl packages or latex. There might |
| 9 |
> be more. |
| 10 |
|
| 11 |
In addition to what the others have said, FEATURES= ?? AFAIK, FEATURES |
| 12 |
is PM-implementation-specific and not part of PMS. It's not something |
| 13 |
ebuilds/eclasses should be messing with or care about at all, as it's PM- |
| 14 |
private-implementation domain, not ebuild domain. |
| 15 |
|
| 16 |
Unless you're suggesting changing the portage implementation to care |
| 17 |
about what specific package it's working on, and apply FEATURES based on |
| 18 |
that, and that doesn't sound like a good idea either. |
| 19 |
|
| 20 |
So I'm with the others. Just leave it alone. Being a NOOP for the |
| 21 |
packages in question means it's not hurting anything, and attempting to |
| 22 |
optimize it out is likely to be far more trouble than its worth. |
| 23 |
|
| 24 |
-- |
| 25 |
Duncan - List replies preferred. No HTML msgs. |
| 26 |
"Every nonfree program has a lord, a master -- |
| 27 |
and if you use the program, he is your master." Richard Stallman |
Archives