From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH 6/7] defaults.py: Update all repository, DISTDIR, PKGDIR settings to new /var paths
Date: Fri, 10 Mar 2017 13:02:10 -0800 [thread overview]
Message-ID: <20170310130210.5fc9f3d2.dolsen@gentoo.org> (raw)
In-Reply-To: <20170310123606.5692a8ab.dolsen@gentoo.org>
On Fri, 10 Mar 2017 12:36:06 -0800
Brian Dolbec <dolsen@gentoo.org> wrote:
> On Fri, 10 Mar 2017 11:51:07 -0800
> Zac Medico <zmedico@gentoo.org> wrote:
>
> > On Fri, Mar 10, 2017 at 11:23 AM, Brian Dolbec <dolsen@gentoo.org>
> > wrote:
> > > @@ -75,8 +75,8 @@ TARGET_MOUNT_DEFAULTS = {
> > > "distdir": "/usr/portage/distfiles",
> > > "icecream": "/usr/lib/icecc/bin",
> > > "kerncache": "/tmp/kerncache",
> > > - "packagedir": "/usr/portage/packages",
> > > - "portdir": "/usr/portage",
> > > + "packagedir": "/var/portage/packages",
> > > + "portdir": "/var/portage/repos",
> > > "port_tmpdir": "/var/tmp/portage",
> > > "port_logdir": "/var/log/portage",
> > > "proc": "/proc",
> > > @@ -86,8 +86,8 @@ TARGET_MOUNT_DEFAULTS = {
> > > SOURCE_MOUNT_DEFAULTS = {
> > > "dev": "/dev",
> > > "devpts": "/dev/pts",
> > > - "distdir": "/usr/portage/distfiles",
> > > - "portdir": "/usr/portage",
> > > + "distdir": "/var/portage/distfiles",
> > > + "portdir": "/var/portage/repos",
> > > "port_tmpdir": "tmpfs",
> > > "proc": "/proc",
> > > "shm": "shmfs",
> >
> > Shouldn't those portdir settings be /var/portage/repos/gentoo or
> > something like that?
>
> No, that is the base directory for it to unpack or rsync the repo to.
> It is a little confusing because of the way the code was written
> before. I'll have to get in there and rename that to 'reposdir' to
> better reflect the way it is used.
>
> Note, those settings were only temporary for testing that the code was
> ready for relocation. I think I'll change them to /var/gentoo as the
> base for now. Then we can change them when the council has decreed
> the final location.
>
Also, with these code changes, it completely separates the source host
system source tree used to generate the snapshot and the target
location and name of the snapshot tree and it's new location during
stage generation. The new stage will end up with the new settings in
its make.conf. This makes it possible for a host with
traditional /usr/portage or any other location or name to generate a
snapshot with a completely different base repo name. This will make it
possible for the infra severs generating the snapshot and stages to not
need to be migrated to the new defaults in order to generate the
snapshots and stages with the new settings. In fact, using an
alternate config, the same servers could generate both old (portage) and
new (gentoo) snapshots for an interim if desired. Well, I think the
snapshots should be to give time for users to migrate their systems for
the new tree directory name. That is if this code is used to generate
the daily tree snapshots.
One thing to note is that you must first edit the catalyst.conf to
add/edit the new config variables, then generate a new snapshot before
doing stage runs.
repo_basedir="/usr"
repo_name="portage"
target_distdir="/usr/portage/distfiles"
target_pkgdir="/usr/portage/packages"
Using these settings, creates a snapshot and make.conf with the
traditional locations directory names. And completely overrides the
new defaults.
Changing the reponame to "gentoo" requires you first generate a
snapshot (the repo_name is used as the target dir and in the final
tarball name). The stage building process will look for the snapshot
with that same name and specified version.
So, derivative distros could more easily use catalyst to generate their
own stages and snapshots. Not to mention gentoo change locations and
repo names to something new without needing code changes to do so. It
would be a simple config edit.
--
Brian Dolbec <dolsen>
next prev parent reply other threads:[~2017-03-10 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 19:22 [gentoo-catalyst] [PATCH 0/7] Latest pending branch fixes Brian Dolbec
2017-03-10 19:22 ` [gentoo-catalyst] [PATCH 1/7] Move the signal handler into the StageBase class so it can handle unbind() cleanup Brian Dolbec
2017-03-11 21:31 ` Mike Frysinger
2017-03-10 19:23 ` [gentoo-catalyst] [PATCH 6/7] defaults.py: Update all repository, DISTDIR, PKGDIR settings to new /var paths Brian Dolbec
2017-03-10 19:51 ` Zac Medico
2017-03-10 20:36 ` Brian Dolbec
2017-03-10 21:02 ` Brian Dolbec [this message]
2017-03-20 9:02 ` Mike Frysinger
2017-03-20 9:21 ` Brian Dolbec
2017-03-20 9:32 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170310130210.5fc9f3d2.dolsen@gentoo.org \
--to=dolsen@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox