| 1 |
On Tue, Jan 17, 2017 at 04:45:39AM -0800, Daniel Campbell wrote: |
| 2 |
> On 01/06/2017 12:46 PM, William L. Thomson Jr. wrote: |
| 3 |
> > On Friday, January 6, 2017 9:14:54 AM EST Alec Warner wrote: |
| 4 |
> >> |
| 5 |
> >> The nice thing about ::graveyard or similar is that its a clear demarcation |
| 6 |
> >> between maintained (in tree) and unmaintained (graveyard.) It also means |
| 7 |
> >> that people doing actual maintenance work can basically ignore the |
| 8 |
> >> graveyard as a matter of policy. The ebuilds are archived there (for users) |
| 9 |
> >> but since they are unmaintained they may not work correctly. |
| 10 |
> > |
| 11 |
> > This is what the Java team used to do. There was a java-graveyard-overlay. I |
| 12 |
> > do not believe any package ever moved there came back into the tree. It did |
| 13 |
> > result in a pretty messed up overlay, but makes it a user problem. |
| 14 |
> > |
| 15 |
> > At the same time, something could always be restored from VC. Not like removal |
| 16 |
> > is removing all history and traces. Thus not sure such overlay is really even |
| 17 |
> > beneficial. Using it could cause lots of problems if they just care about 1 |
| 18 |
> > package or a few. |
| 19 |
> > |
| 20 |
> |
| 21 |
> There's a nice trick around that, actually: let's assume the overlay is |
| 22 |
> called "foo-overlay". |
| 23 |
> |
| 24 |
> In package.mask: |
| 25 |
> |
| 26 |
> */*::foo-overlay |
| 27 |
> |
| 28 |
> will mask all packages in the overlay. You can then add packages to |
| 29 |
> package.unmask: |
| 30 |
> |
| 31 |
> pkg-cat/foobar::foo-overlay |
| 32 |
> |
| 33 |
> That should alleviate most issues, though it can make dependencies a |
| 34 |
> PITA if those deps are also in the overlay. In that case, emerge should |
| 35 |
> yell at you and suggest adding lines to package.unmask. |
| 36 |
|
| 37 |
Another option would be to set the priority of the overlay to -1001 (one |
| 38 |
less than gentoo.git) and explicitly emerge the package from the |
| 39 |
overlay: |
| 40 |
|
| 41 |
emerge -a pkg-cat/foobar::foo-overlay |
| 42 |
|
| 43 |
Dependencies will by default be drawn from gentoo.git (if it has equal |
| 44 |
or better version(s)), and overlay-only dependencies won't need to be |
| 45 |
explicitly unmasked. |
| 46 |
|
| 47 |
You may end up with gentoo.git-provided packages coming from the overlay |
| 48 |
if they have newer versions, though when talking about graveyard, that |
| 49 |
shouldn't be an issue. |
| 50 |
|
| 51 |
-- |
| 52 |
Sam Jorna (wraeth) |
| 53 |
GPG ID: 0xD6180C26 |
Archives