| 1 |
On 14/11/14 01:36, Ulrich Mueller wrote: |
| 2 |
>>>>>> On Thu, 13 Nov 2014, Michael Palimaka wrote: |
| 3 |
> |
| 4 |
>> Suggested policy to get the ball rolling: |
| 5 |
> |
| 6 |
>> In general, a package must explicitly depend upon what it directly |
| 7 |
>> uses. However, to avoid ebuild complexity and developer burden there |
| 8 |
>> are some exceptions. Packages that appear in the base system set may |
| 9 |
>> be omitted from an ebuild's dependency list in the following |
| 10 |
>> circumstances: |
| 11 |
> |
| 12 |
>> * C compiler and runtime |
| 13 |
> |
| 14 |
>> * C++ compiler and runtime |
| 15 |
> |
| 16 |
>> * A POSIX-compliant shell |
| 17 |
> |
| 18 |
>> * bash, baselayout, binutils, coreutils, findutils, grep, make |
| 19 |
> |
| 20 |
> awk? diffutils? texinfo? |
| 21 |
|
| 22 |
I have no particular opinion on what should be included (or even if we |
| 23 |
should have a whitelist - I am mainly interested in capturing library |
| 24 |
usage). If we do have a whitelist, it would be useful to figure out what |
| 25 |
in @system is intended to be actually be part of the base system and |
| 26 |
what is there for convenience (eg. virtual/ssh). |
Archives