public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: [RFC] New GLEP: file installation masks
Date: Wed, 8 Jun 2016 08:37:30 +0200	[thread overview]
Message-ID: <20160608083730.411f8140.mgorny@gentoo.org> (raw)
In-Reply-To: <22359.44157.475779.594768@a1i15.kph.uni-mainz.de>

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

On Wed, 8 Jun 2016 07:26:21 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:

> >>>>> On Fri, 20 May 2016, Michał Górny wrote:  
> 
> > Sometime around a year ago, I started working on extending
> > INSTALL_MASK to support well-defined locations. The work was never
> > finished, and I just found my old specification for it. I've cleaned
> > it up a bit, and extended it into a complete GLEP covering
> > INSTALL_MASK [1].  
> 
> > Please review the specification provided. The basic goal is to
> > provide an ability to use INSTALL_MASK alike USE flags -- with path
> > groups that are well-defined and described in the repository.  
> 
> Sorry, I am late in the game. (Or maybe not, since the GLEP doesn't
> yet have a number.)
> 
> The GLEP says that path groups always apply globally. So the
> install-mask.conf file is not "alike layout.conf" (as the GLEP claims)
> because its scope is not restricted to the repository where it is
> stored. And in turn this can lead to name collisions ("Duplicate
> groups [...] are considered an error").
> 
> Therefore I think that repository metadata is the wrong place for
> storing the install-mask.conf file. It is configuration, specific to
> Portage (but not to the repository), so /usr/share/portage/config/
> would be a better location to store it. 

...which would mean we have to re-release Portage every time it
changes, which in turn means we can't do anything without having shout
at users to upgrade Portage, and upgrade, and upgrade...

systemd uses new path? Upgrade Portage. We support a new localization?
Upgrade Portage. We failed horribly and your system no longer boots?
Upgrade Portage.

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>

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

  reply	other threads:[~2016-06-08  6:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 14:01 [gentoo-dev] [RFC] New GLEP: file installation masks Michał Górny
2016-05-20 15:12 ` Michael Orlitzky
2016-05-20 15:21   ` Michał Górny
2016-05-20 15:30     ` Michael Orlitzky
2016-05-20 15:44       ` Michał Górny
2016-05-20 16:15         ` Michael Orlitzky
2016-05-20 16:48           ` Michał Górny
2016-05-20 17:34             ` Michael Orlitzky
2016-05-29 12:54               ` Michał Górny
2016-05-20 15:34 ` Daniel Campbell
2016-05-20 15:40   ` Michael Orlitzky
2016-05-20 15:49     ` Michał Górny
2016-05-20 20:00       ` Ian Stakenvicius
2016-05-20 21:11         ` Michał Górny
2016-06-08  5:26 ` [gentoo-dev] " Ulrich Mueller
2016-06-08  6:37   ` Michał Górny [this message]
2016-06-08  7:17     ` Ulrich Mueller
2016-06-08  8:01       ` Michał Górny
2016-06-08  8:33         ` Ulrich Mueller
2016-06-08 13:14           ` Michał Górny

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=20160608083730.411f8140.mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ulm@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