1 |
On Mon, 2013-07-22 at 00:35 +0200, hasufell wrote: |
2 |
> On 07/22/2013 12:33 AM, Michał Górny wrote: |
3 |
> > Dnia 2013-07-22, o godz. 00:16:31 hasufell <hasufell@g.o> |
4 |
> > napisał(a): |
5 |
> > |
6 |
> >> On 07/22/2013 12:07 AM, Duncan wrote: |
7 |
> >>> hasufell posted on Sun, 21 Jul 2013 17:22:24 +0200 as |
8 |
> >>> excerpted: |
9 |
> >>> |
10 |
> >>>> solution: Treeclean it and maintain it in an overlay (maybe |
11 |
> >>>> science-overlay). That's exactly what overlays are for... |
12 |
> >>>> experimental stuff. |
13 |
> >>> |
14 |
> >>> What's the pros/cons of overlay vs. in-tree-but-masked for |
15 |
> >>> something like this? In-tree-but-masked is at least available |
16 |
> >>> for those who want it, without having to load an overlay, but I |
17 |
> >>> don't see that discussed at all, here. |
18 |
> >>> |
19 |
> >> |
20 |
> >> cons: - users have to run "layman -a foo" ...I hope they will |
21 |
> >> manage (and the masking reason will be updated to explain where |
22 |
> >> to look for googleearth ebuilds) |
23 |
> > |
24 |
> > Then to get *a single package* they start using the whole overlay. |
25 |
> > If it's a sane overlay, fine. But some overlays really replace a |
26 |
> > lot of stuff silently and trigger failures we didn't even imagine |
27 |
> > before. |
28 |
> > |
29 |
> |
30 |
> No. |
31 |
> |
32 |
> I'd either use a separate single-purpose overlay or add it to |
33 |
> science-overlay. |
34 |
|
35 |
|
36 |
If it's a separate overlay, then googleearth overlay in gentoo's github |
37 |
account for easy access for users, both to get and contribute. |