Gentoo Archives: gentoo-dev

From: William Hubbs <williamh@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] rfc: moving default location of portage tree
Date: Wed, 11 Jul 2018 20:42:33
Message-Id: 20180711204225.GA497@linux1.home
In Reply to: Re: [gentoo-dev] rfc: moving default location of portage tree by Richard Yao
1 On Wed, Jul 11, 2018 at 04:25:20PM -0400, Richard Yao wrote:
2 > On 07/11/2018 03:29 AM, Jory A. Pratt wrote:
3 > > On 07/10/18 16:35, M. J. Everitt wrote:
4 > >> On 10/07/18 21:09, William Hubbs wrote:
5 > >>> On Mon, Jul 09, 2018 at 03:54:35PM -0700, Zac Medico wrote:
6 > >>>> On 07/09/2018 03:27 PM, M. J. Everitt wrote:
7 > >>>>> On 09/07/18 23:12, Zac Medico wrote:
8 > >>>>>> On 07/09/2018 02:34 PM, Kristian Fiskerstrand wrote:
9 > >>>>>>> I'd mostly argue any such change should only affect new systems
10 > >>>>>>>
11 > >>>>>> Yes, changing defaults for existing systems would be annoying.
12 > >>>>>>
13 > >>>>>> My recommendation is to have catalyst set the new defaults in the stage
14 > >>>>>> tarballs.
15 > >>>>>>
16 > >>>>>> When sys-apps/portage changes its internal defaults, I'd like for the
17 > >>>>>> upgrade process to call a tool that generates configuration files when
18 > >>>>>> necessary to ensure that the existing paths remain constant.
19 > >>>>> I think it should be possible for RelEng to make a start on catalyst
20 > >>>>> updates - is there anything that would inhibit going ahead with this,
21 > >>>>> potentially?
22 > >>>> No, nothing. Whatever catalyst puts it the default config will become
23 > >>>> our new default.
24 > >>> I would still like to see notice about what the new defaults are and how
25 > >>> to migrate current systems to them.
26 > >>>
27 > >>>
28 > >>> Thanks,
29 > >>>
30 > >>> William
31 > >>>
32 > >>>> --
33 > >>>> Thanks,
34 > >>>> Zac
35 > >>>>
36 > >>>
37 > >>>
38 > >> I'd like to propose that further to the discussion here on the -dev
39 > >> mailing list, the Council discuss and make a firm proposal on the new
40 > >> default paths, and then RelEng can make the appropriate updates to the
41 > >> catalyst builds. A news item can be compiled, with an appropriate wiki
42 > >> article perhaps on migration strategy (I may volunteer to format such a
43 > >> page with some appropriate guidance).
44 > >> Regards,
45 > >> Michael / veremitz.
46 > >>
47 > > This is a mess, many systems are setup with portage already on a
48 > > seperate partition for reasons. What advantage does it provide to move
49 > > the tree now after all these years? I have seen nothing more then lets
50 > > do this cause I like the ideal lately and it is getting old, there is no
51 > > benefit that would justify moving the tree or many other changes that
52 > > are being made in Gentoo lately.
53 >
54 > People who want to move it could just set PORTDIR in make.conf. I don't
55 > see any reason to move it either.
56
57 Actually, I believe that PORTDIR is becoming a thing of the past.
58
59 Also, the default definitely should not be on /usr per fhs. This would
60 allow /usr to be mounted read only.
61 This doesn't affect things like the example above where /usr/portage is
62 a mount point.
63
64 > >
65 > >
66 > >
67 >
68 >

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies