public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam Jorna <wraeth@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: Why lastrite when it works? (Was: Re: [gentoo-dev] Packages up for grabs due to retirement)
Date: Wed, 18 Jan 2017 18:48:39 +1100	[thread overview]
Message-ID: <20170118074837.GA2607@titan.wraeth.lan> (raw)
In-Reply-To: <c8d26356-79ff-baae-3cce-023cb2de51d2@gentoo.org>

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

On Tue, Jan 17, 2017 at 04:45:39AM -0800, Daniel Campbell wrote:
> On 01/06/2017 12:46 PM, William L. Thomson Jr. wrote:
> > On Friday, January 6, 2017 9:14:54 AM EST Alec Warner wrote:
> >>
> >> The nice thing about ::graveyard or similar is that its a clear demarcation
> >> between maintained (in tree) and unmaintained (graveyard.) It also means
> >> that people doing actual maintenance work can basically ignore the
> >> graveyard as a matter of policy. The ebuilds are archived there (for users)
> >> but since they are unmaintained they may not work correctly.
> > 
> > This is what the Java team used to do. There was a java-graveyard-overlay. I 
> > do not believe any package ever moved there came back into the tree. It did 
> > result in a pretty messed up overlay, but makes it a user problem.
> > 
> > At the same time, something could always be restored from VC. Not like removal 
> > is removing all history and traces. Thus not sure such overlay is really even 
> > beneficial. Using it could cause lots of problems if they just care about 1 
> > package or a few.
> > 
> 
> There's a nice trick around that, actually: let's assume the overlay is
> called "foo-overlay".
> 
> In package.mask:
> 
>     */*::foo-overlay
> 
> will mask all packages in the overlay. You can then add packages to
> package.unmask:
> 
>     pkg-cat/foobar::foo-overlay
> 
> That should alleviate most issues, though it can make dependencies a
> PITA if those deps are also in the overlay. In that case, emerge should
> yell at you and suggest adding lines to package.unmask.

Another option would be to set the priority of the overlay to -1001 (one
less than gentoo.git) and explicitly emerge the package from the
overlay:

emerge -a pkg-cat/foobar::foo-overlay

Dependencies will by default be drawn from gentoo.git (if it has equal
or better version(s)), and overlay-only dependencies won't need to be
explicitly unmasked.

You may end up with gentoo.git-provided packages coming from the overlay
if they have newer versions, though when talking about graveyard, that
shouldn't be an issue.

-- 
Sam Jorna (wraeth)
GPG ID: 0xD6180C26


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

  reply	other threads:[~2017-01-18  7:48 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-31 21:54 [gentoo-dev] Packages up for grabs due to retirement Thomas Kahle
2016-12-31 23:00 ` James Le Cuirot
2017-01-01  9:42   ` Thomas Kahle
2017-01-01  9:54     ` James Le Cuirot
2017-01-01  9:48 ` [gentoo-dev] " David Seifert
2017-01-01 10:08   ` Thomas Kahle
2017-01-01 17:16 ` [gentoo-dev] " Lars Wendler
2017-01-02 19:53   ` Brian Evans
2017-01-03  9:00     ` grozin
2017-01-03 11:05       ` Michał Górny
2017-01-03 14:14         ` Why lastrite when it works? (Was: Re: [gentoo-dev] Packages up for grabs due to retirement) Michael Mol
2017-01-03 14:24           ` Damien LEVAC
2017-01-03 14:57             ` Michael Mol
2017-01-03 15:10               ` Kristian Fiskerstrand
2017-01-03 17:10                 ` Matthew Thode
2017-01-03 15:11               ` Damien LEVAC
2017-01-03 17:07                 ` Matthew Thode
2017-01-03 15:12               ` M. J. Everitt
2017-01-03 15:23               ` Rich Freeman
2017-01-03 15:41                 ` Alice Ferrazzi
2017-01-03 16:59                   ` james
2017-01-03 16:09                 ` Michael Mol
2017-01-03 16:29                   ` Rich Freeman
2017-01-06  4:27                 ` Kent Fredric
2017-01-06 14:13                   ` Michael Mol
2017-01-06 20:51                     ` William L. Thomson Jr.
2017-01-06 15:01                   ` Rich Freeman
2017-01-07  2:51                     ` M. J. Everitt
2017-01-06 17:14                   ` Alec Warner
2017-01-06 17:26                     ` Rich Freeman
2017-01-06 20:46                     ` William L. Thomson Jr.
2017-01-17 12:45                       ` Daniel Campbell
2017-01-18  7:48                         ` Sam Jorna [this message]
2017-01-07  2:58                     ` M. J. Everitt
2017-01-07  2:47                   ` M. J. Everitt
2017-01-04 10:34             ` Thomas Kahle
2017-01-03 14:31         ` [gentoo-dev] Packages up for grabs due to retirement M. J. Everitt
2017-01-03 14:34           ` Damien LEVAC
2017-01-04  3:11             ` Mart Raudsepp
2017-01-06  4:33               ` Kent Fredric
2017-01-06  6:00           ` Daniel Campbell
2017-01-06  8:04             ` Mart Raudsepp
2017-01-03 11:14       ` Lars Wendler

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=20170118074837.GA2607@titan.wraeth.lan \
    --to=wraeth@gentoo.org \
    --cc=gentoo-dev@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