1 |
On Wed, Jan 18, 2012 at 10:05 PM, Mike Frysinger <vapier@g.o> wrote: |
2 |
> if it's part of the implicit system dep, they absolutely need to defend their |
3 |
> actions. you want to change the policy, then start a thread on it. |
4 |
|
5 |
What policy? I don't see any written policy stating that you aren't |
6 |
allowed to include system packages in *DEPEND. |
7 |
|
8 |
There is a line in the devmanual stating that it is "not necessary, |
9 |
nor advisable,..." to list some kinds of system dependencies, full of |
10 |
caveats about the system set varying by profile and specific versions |
11 |
and such. It does not say that it is not permitted. |
12 |
|
13 |
So, I don't really see any policy to change. Anybody wanting to |
14 |
create such a policy is of course welcome to start a thread on it... |
15 |
:) |
16 |
|
17 |
Rich |