Gentoo Archives: gentoo-project

From: Markos Chandras <hwoarang@g.o>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] Introducing an optional files directory in the Portage tree with an embedded install condition and individual maintainers. (was Re: [gentoo-project] Proposal for add-on file utility (run after emerge update))
Date: Mon, 17 Jun 2013 13:38:48
Message-Id: CAG2jQ8hsHrxXsVkNpXm__Br2LYpz9RjEi-A2gvy5TVABkvGBDw@mail.gmail.com
In Reply to: Re: [gentoo-project] Introducing an optional files directory in the Portage tree with an embedded install condition and individual maintainers. (was Re: [gentoo-project] Proposal for add-on file utility (run after emerge update)) by Tom Wijsman
1 On 16 June 2013 23:02, Tom Wijsman <TomWij@g.o> wrote:
2 > On Sun, 16 Jun 2013 15:31:10 -0400
3 > Rich Freeman <rich0@g.o> wrote:
4 >
5 >> On Sun, Jun 16, 2013 at 3:22 PM, Tom Wijsman <TomWij@g.o>
6 >> wrote:
7 >> > Either by denoting USE flags in USE as special _or_ introducing a
8 >> > separate OUSE variable.
9 >> >
10 >> > They don't have to be "openrc", "cron", "systemd" but could be like
11 >> > "init-scripts", "cron-files", "systemd-units"; to not collide with
12 >> > any existing USE flags, if any.
13 >> >
14 >> > Do they start to depend on each other? Why?
15 >>
16 >> Bottom line is that in order to accomplish any of this we need to
17 >> expand PMS to specify a syntax, implement this stuff in portage, and
18 >> then start modifying all our ebuilds so that heaven-forbid you don't
19 >> get an openrc script installed if you don't set USE=openrc.
20 >>
21 >> I don't think any of this is worth it for a one block text file.
22 >
23
24 I believe this proposal aims to workaround the "we can't work
25 together" problem than actually providing
26 real benefit to the way we maintain packages.
27
28 --
29 Regards,
30 Markos Chandras - Gentoo Linux Developer
31 http://dev.gentoo.org/~hwoarang

Replies