public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@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: Mon, 20 Mar 2017 05:32:58 -0400	[thread overview]
Message-ID: <20170320093258.GD24205@vapier> (raw)
In-Reply-To: <20170320022152.30067ab2.dolsen@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2181 bytes --]

On 20 Mar 2017 02:21, Brian Dolbec wrote:
> On Mon, 20 Mar 2017 05:02:18 -0400 Mike Frysinger wrote:
> > On 10 Mar 2017 11:23, Brian Dolbec wrote:
> > > -	"distdir": "/usr/portage/distfiles",
> > > +	"distdir": "/var/portage/distfiles",
> > > -	"local_overlay": "/usr/local/portage",
> > > +	"local_overlay": "/var/portage/repos/local",
> > > -	"packagedir": "/usr/portage/packages",
> > > +	"packagedir": "/var/portage/packages",
> > > -	"portdir": "/usr/portage",
> > > +	"portdir": "/var/portage/repos",
> > > -	"repo_basedir": "/usr",
> > > +	"repo_basedir": "/var/portage/repos",  
> > 
> > sticking everything under /var/portage doesn't seem like an
> > improvement to me.  where was the discussion that ended up with these
> > values ?  seems like it should be:
> > 	repo_basedir:  /var/lib/portage/repos/
> > 	portdir:       /var/lib/portage/repos/gentoo/
> > 	local_overlay: /var/lib/portage/repos/local/
> > 	packagedir:    /var/lib/portage/packages/
> > 	distdir:       /var/cache/portage/distfiles/
> 
> your behind the times, I changed it to /var/gentoo as the base in the
> pending branch.  The main idea is to keep the path short as possible I
> think
> 
> They were just temporary anyway.  But that is also what work sets them
> under.  Personally I put them under /var/db on my machine, where the
> vardb is stored.  But lately, I pretty much just use teh git tree wich
> is in a subdir of my user home directory.
> 
> The original email thread in -dev a few years ago never could come to
> any kind of consensus where the new default should be.  It is going to
> have to be a council decision to set the new default.
> 
> We'll have to  send a new email to the list with the main options, try
> to get them to vote on their preference, just to satisfy council before
> they make a choice.
> 
> I need to send a couple more patches to the list.  But I need to get a
> couple things cleared up first.

OK, as long as we don't go merging these patches into master until we've
settled on the desired defaults.  it doesn't make sense to have catalyst
do one thing since it is effectively the default install state.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-03-20  9:33 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
2017-03-20  9:02   ` Mike Frysinger
2017-03-20  9:21     ` Brian Dolbec
2017-03-20  9:32       ` Mike Frysinger [this message]

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=20170320093258.GD24205@vapier \
    --to=vapier@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