public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2018-07-29
Date: Fri, 13 Jul 2018 20:23:28 -0700	[thread overview]
Message-ID: <20180713202328.338edb6b@professor-x> (raw)
In-Reply-To: <23368.58952.48436.482420@a1i15.kph.uni-mainz.de>

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

On Fri, 13 Jul 2018 19:50:00 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:

> >>>>> On Fri, 13 Jul 2018, Brian Dolbec wrote:  
> 
> > I would like the council to put an end to the current "moving
> > default location of portage tree" bikeshed thread by making the
> > decision of our new defaults.  
> 
> I think we should have proposal ready for vote at the council meeting,
> because I don't expect that discussion of individual paths during the
> meeting would lead to anything.
> 
> > This includes:
> > 	- main "gentoo" ebuild tree
> > 	- distfiles
> > 	- packages  
> 
> Trying to summarise the discussion in -dev, and in #-portage: Everyone
> seems to agree that all of these should be somewhere under /var, and
> possible candidates are /var/lib, /var/cache, and /var/db. Note that
> /var/db is not specified by the FHS, but it exists in all the BSDs.
> Also, I am disregarding suggestions like /var/gentoo or /var/portage
> for now.
> 
> For both /var/lib and /var/cache the FHS requires a <package>
> subdirectory. Unless we want this to be "portage", we could use
> "package-manager" (since virtual/package-manager is a package),
> or pretend that "pm" is an alias for it. This would lead us to the
> following paths, respectively:
> 
>    /var/lib/{package-manager,pm}/gentoo
>    /var/cache/{package-manager,pm}/distfiles
>    /var/cache/{package-manager,pm}/packages
>

I think it is a mistake to group distfiles and packages directly
beside the repositories.  

One of the big reasons I feel this way, is so that configuration can be
made more plugin friendly.  With all repositories under one subdir. It
could be possible for a package manager to scan the subdir for
repositories.  Details of repo configuration data may be included in the
repository.  This could eliminate the need for a
/etc/portage/repos.conf. Or at the very least, eliminate the need to
specify location if it is in the default base path. (just food for
thought)

 If under the same /var/lib/pm, then the
repositories should be in it's own "repos" subdir still for the above
mentioned reasons, just like the example  below for /var/db/.   If that
puts more weight on the /var/db prefix due to FHS..., then that is
fine, it just happens to be my configuration already ;)


> Alternatively, we could place either the gentoo tree, or all three of
> the above under /var/db (which doesn't follow the FHS, so no subdir
> requirement):
> 
>    /var/db/repos/gentoo
>    /var/db/distfiles
>    /var/db/packages
> 
> > 	- snapshot name  
> 
> Simply gentoo-20180712.tar.xz instead of portage-20180712.tar.xz?
> Or is that not specific enough?
> 
> Ulrich

snapshot name is good and follows the repo naming convention. :)


Which ever of the above locations that becomes the default, I would
change layman to the new default repos location as well.


-- 
Brian Dolbec <dolsen>


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  parent reply	other threads:[~2018-07-14  3:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13  8:37 [gentoo-project] Call for agenda items - Council meeting 2018-07-29 Ulrich Mueller
2018-07-13  9:48 ` Michał Górny
2018-07-13 13:57 ` Brian Dolbec
2018-07-13 17:50   ` Ulrich Mueller
2018-07-13 17:59     ` Kristian Fiskerstrand
2018-07-13 18:12       ` Ulrich Mueller
2018-07-13 18:19         ` Raymond Jennings
2018-07-13 18:25           ` M. J. Everitt
2018-07-13 18:28       ` M. J. Everitt
2018-07-13 18:43     ` Rich Freeman
2018-07-13 19:20       ` Ulrich Mueller
2018-07-13 19:33         ` Alec Warner
2018-07-13 19:41         ` Rich Freeman
2018-07-13 20:24           ` Ulrich Mueller
2018-07-13 19:51     ` Michał Górny
2018-07-14  3:23     ` Brian Dolbec [this message]
2018-07-14 16:21 ` Manuel Rüger
2018-07-14 17:33   ` William Hubbs
2018-07-14 17:47     ` Manuel Rüger
2018-07-14 18:06       ` William Hubbs
2018-07-14 18:38       ` Ulrich Mueller
2018-07-14 18:49         ` Manuel Rüger
2018-07-14 20:37           ` William Hubbs
2018-07-15 13:17             ` Kristian Fiskerstrand
2018-07-14 19:10   ` Michał Górny
2018-07-14 19:29     ` Matthew Thode
2018-07-14 20:50       ` Michał Górny
2018-07-14 21:15         ` Manuel Rüger

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=20180713202328.338edb6b@professor-x \
    --to=dolsen@gentoo.org \
    --cc=gentoo-project@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