1 |
On Wed, Apr 24, 2013 at 01:34:36PM -0400, Mike Frysinger wrote: |
2 |
> On Wednesday 24 April 2013 13:23:23 William Hubbs wrote: |
3 |
> > On Wed, Apr 24, 2013 at 12:58:21PM -0400, Ian Stakenvicius wrote: |
4 |
> > > On 24/04/13 12:16 PM, William Hubbs wrote: |
5 |
> > > > it has been suggested that gentoo's oldnet scripts be split out |
6 |
> > > > into their own package separate from OpenRC so that they can be |
7 |
> > > > developed independently. I am looking at doing this for OpenRC |
8 |
> > > > 0.12, which I hope to release soon. |
9 |
> > > > |
10 |
> > > > This means when you emerge or upgrade to openrc-0.12, the net.* |
11 |
> > > > scripts will no longer be included. I am going to call the separate |
12 |
> > > > package that includes these scripts gentoo-oldnet. |
13 |
> > > > |
14 |
> > > > My plan is to write a newsitem when OpenRC 0.12 is released |
15 |
> > > > telling users this and that they will have to emerge gentoo-oldnet |
16 |
> > > > to get the gentoo networking scripts or turn on the newnet (maybe |
17 |
> > > > I'll change this to net) use flag to get OpenRC's network scripts |
18 |
> > > > installed and put ewarns in the ebuild if this use flag is turned |
19 |
> > > > off. |
20 |
> > > > |
21 |
> > > > I feel that a newsitem and ewarns in the OpenRC ebuild cover live |
22 |
> > > > systems well. In a nutshell, users should pay attention to their |
23 |
> > > > news items and ewarns. |
24 |
> > > > |
25 |
> > > > On the other hand, some are suggesting that I should add a runtime |
26 |
> > > > dependency to OpenRC so that it pulls in gentoo-oldnet. Since |
27 |
> > > > OpenRC doesn't need gentoo-oldnet in order to run, I feel like this |
28 |
> > > > would be abusing dependencies. |
29 |
> > > > |
30 |
> > > > Does anyone have any thoughts? |
31 |
> > > |
32 |
> > > Current users should be able to do a -uDN and still have their |
33 |
> > > existing systems work as-is. Whether you do this via a static |
34 |
> > > dependency or one controlled by a use flag (and be sure use flag |
35 |
> > > defaults would have oldnet installed by default) is up to you. |
36 |
> > |
37 |
> > The issue is that OpenRC does not have any kind of dependency on |
38 |
> > gentoo-oldnet at all. There will be a separate loopback script in OpenRC |
39 |
> > so it is possible to run OpenRC on a system without the oldnet or |
40 |
> > newnet scripts. In fact, this is a completely valid configuration. |
41 |
> > |
42 |
> > OpenRC doesn't "link" to gentoo-oldnet in any way, so there is no |
43 |
> > dependency. |
44 |
> > |
45 |
> > The way I read the dev manual [1], a newsitem and postinst messages are |
46 |
> > the way to go for somethinglike this. |
47 |
> |
48 |
> it is reasonable to expect openrc updates to *not* break a system. that means |
49 |
> people shouldn't be required to read a news/postinst message to keep from |
50 |
> killing things. |
51 |
> |
52 |
> even then, a default Gentoo system should have networking support available by |
53 |
> default. our manuals assume this, and people shouldn't have to install a |
54 |
> stage3 and then do `emerge gentoo-oldnet` just to have that happen. so |
55 |
> keeping a dependency in openrc (perhaps initially hard, or behind |
56 |
> IUSE=+oldnet) makes sense. |
57 |
|
58 |
I was planning on opening a bug before all of this hit stable to have |
59 |
releng add gentoo-oldnet to the stages when it does hit stable. |
60 |
|
61 |
if we keep a dependency for a while, even behind something like |
62 |
IUSE="+oldnet", when we drop it, people will still be hit if they do |
63 |
emerge --depclean before they emerge gentoo-oldnet. |
64 |
|
65 |
Also, (although I don't really care about this much because we tell people |
66 |
not to do it), folks who set USE="-* foo bar bas" in their make.conf would |
67 |
get hit immediately with this solution. |
68 |
|
69 |
Am I missing something? It just seems like this is putting off the |
70 |
emerge command people will need to run for a while. |
71 |
|
72 |
William |