1 |
On Fri, Nov 14, 2014 at 7:20 AM, Anthony G. Basile <blueness@g.o> wrote: |
2 |
> |
3 |
> Sorry Zac, I posted my reply before I read this. This is essentially the |
4 |
> point I was making. However, I think this will be cumbersome. With the |
5 |
> current way we do things, its easy to delete packages from @system by just |
6 |
> doing '-*sys-apps/man-pages' (for example) in a profile's packages file. It |
7 |
> is not so easy to delete from a DEPEND string, so I foresee some tricky if |
8 |
> logic here. |
9 |
> |
10 |
|
11 |
Appreciating that we're on a slight tangent, why are these packages |
12 |
typically removed? Were they ever truly dependencies? I can't |
13 |
imagine too many packages breaking if man-pages isn't present. |
14 |
|
15 |
If we went the virtual route I would suggest that we end up having a |
16 |
few meta-virtuals. There would be the lazy dependency virtual that |
17 |
pulls in stuff like gcc/libc/posix/etc. There would be a virtual that |
18 |
pulls in useful-to-user stuff like ssh/man-pages/etc. Then there |
19 |
would be a virtual that pulls in both of the other virtuals. Ebuilds |
20 |
would only pull in the dependency virtual. |
21 |
|
22 |
I agree that this would involve a fair bit of work, though I imagine |
23 |
it could be done without any changes to portage insofar as testing |
24 |
things out goes (just create a virtual, stick it in @system in a |
25 |
profile, and test away). |
26 |
|
27 |
-- |
28 |
Rich |