1 |
On Wed, Aug 15, 2012 at 2:21 PM, Duncan <1i5t5.duncan@×××.net> wrote: |
2 |
> |
3 |
> Rich Freeman posted on Wed, 15 Aug 2012 06:27:41 -0400 as excerpted: |
4 |
> |
5 |
> > Right now having decent KDE and Gnome support with all the bells and |
6 |
> > whistles[...] isn't that hard, [It] will likely get harder, which means |
7 |
> > in practice what we'll probably have is a reasonable compromise which |
8 |
> > will never be quite as polished in any one direction as it could be, |
9 |
> > unless the end user does the polishing. |
10 |
> |
11 |
> Well stated. |
12 |
> |
13 |
> > RE you concerns about OpenRC being in @system. Personally I'm a fan of |
14 |
> > getting rid of @system entirely except as something used to build |
15 |
> > install CDs or having some sets for convenience in building systems. It |
16 |
> > only exists for a few reasons that I can think of: |
17 |
> > 1. Devs don't want to have ebuilds that capture dependencies on every |
18 |
> > little thing. A few well-chosen virtuals like "shell utilities" or |
19 |
> > whatever might help with this. |
20 |
> > 2. Things like Prefix rely on the system not installing local copies of |
21 |
> > libraries in the core system it needs to link to. Careful use of |
22 |
> > package.provided in profiles might address this. |
23 |
> > 3. We'd need many more virtuals to handle situations like FreeBSD where |
24 |
> > people don't what GNU on their systems. Right now if they are system |
25 |
> > packages they just define system appropriately and ebuilds don't |
26 |
> > directly pull in the GNU stuff anyway. |
27 |
> |
28 |
> AFAIK, @system also helps resolve a few nasty circular dependencies. In |
29 |
> fact, I believe that's it's primary purpose. As such I'm not sure it's |
30 |
> practical (as opposed to possible, cost/benefit simply makes it |
31 |
> impractical) to entirely get rid of, but it does occur to me that sets |
32 |
> would be an interesting way to go. Define a few sets that together |
33 |
> compose @system as we have it today, and basically package.provide them |
34 |
> during the bootstrap phase. |
35 |
> |
36 |
> AFAIK the original stage tarball also contains a minimal installed tree, |
37 |
> for similar reasons. I'm not actually sure how they interact. That'd be |
38 |
> releng/arch/catalyst territory. |
39 |
|
40 |
Just piping up here, as this relates to an idea that's been |
41 |
percolating through my mind for a couple weeks. |
42 |
|
43 |
I've occasionally noticed portage tell me about circular dependencies, |
44 |
where the most straight forward resolution is to emerge some package |
45 |
in the loop twice. The first time, with a USE flag disabled (avahi and |
46 |
gtk are the usual suspects), and the second time with the USE flag |
47 |
enabled. |
48 |
|
49 |
In circumstances where it's necessary to do something like that to |
50 |
reach a final desired system state, I'm not sure I see any problem |
51 |
with portage automatically doing the two-stage emerge. |
52 |
|
53 |
It also sounds like something like that could be a benefit to shrinking @system. |
54 |
|
55 |
As far as things such as libc, where many, many packages require their |
56 |
use, I don't personally see a problem with recommending that ebuilds |
57 |
depend on them. My only other notable experience for Linux |
58 |
distributions is Debian/Ubuntu, and a quick glance shows 16,389 |
59 |
packages expressing explicit dependencies on libc6 in Ubuntu 12.04. |
60 |
|
61 |
-- |
62 |
:wq |