| 1 |
On Monday 10 October 2005 14:53, Chris Gianelloni wrote: |
| 2 |
> |
| 3 |
> Here's my question... use.local.desc is already package-specific, so why |
| 4 |
> would we need yet *another* place to put package-specific definitions? |
| 5 |
> Would it not be enough to have use.local.desc overlay on use.desc? If |
| 6 |
> package foo uses global USE flag bar in a way different from the |
| 7 |
> description in use.desc, then it should list the USE flag in |
| 8 |
> use.local.desc with the correct description for that package. |
| 9 |
> |
| 10 |
The additionnal info about USE flags should not be what is this or that USE |
| 11 |
flag used differently for, but rather what *exactly* does the use-flag |
| 12 |
influence. What exact features of the program are enabled/disabled/changed by |
| 13 |
the given USE flag. |
| 14 |
Some USE flags are used to either compile against a lib that's shipped with a |
| 15 |
package or with the system version of that lib. Would be useful to know. |
| 16 |
|
| 17 |
Then there are USE flags like static which are very unprecise. Do they mean |
| 18 |
that the program is 100% stand-alone (e.g. does not link against any lib) or |
| 19 |
does it have to do with *.a, *.la files being installed, or just reduce the |
| 20 |
count of libs linked against... |
| 21 |
|
| 22 |
In addition, providing the info in the package metadata is cleaner as |
| 23 |
information about a given package is in one place, and there is not one file |
| 24 |
with 1k lines with many USE flags and their use for each and every package. |
| 25 |
|
| 26 |
The aim is to allow to know what happens without reading the ebuild AND the |
| 27 |
configure script and makefiles of a package. |
| 28 |
|
| 29 |
Bruno |
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-dev@g.o mailing list |
Archives