1 |
On Mon, 14 Sep 2009 20:28:26 +0200 |
2 |
Sebastian Pipping <webmaster@××××××××.org> wrote: |
3 |
> Ciaran McCreesh wrote: |
4 |
> > Because an overlay model has only a single foo-1.2. Think of it like |
5 |
> > stacks of paper. You've got your main repository: |
6 |
> > |
7 |
> > ::gentoo foo-1.1 foo-1.2 foo-1.3 |
8 |
> > |
9 |
> > and on top of that you put your overlay: |
10 |
> > |
11 |
> > ::extras foo-1.2 foo-1.4 |
12 |
> > ::gentoo foo-1.1 foo-1.2 foo-1.3 |
13 |
> > |
14 |
> > and then looking down from the top, all an overlay model package |
15 |
> > manager sees is the foo-1.2 from the overlay. There's no |
16 |
> > foo-1.2::gentoo and foo-1.2::extras, there's just a single foo-1.2 |
17 |
> > that's made from (gentoo + extras). |
18 |
> |
19 |
> I see. So it would not work for dependencies but it should work for |
20 |
> masking. That alone wouldn't make me happy, though. |
21 |
|
22 |
I don't think it would necessarily work for masking either the way |
23 |
Portage sees it (although iirc it would have done for the way Pkgcore |
24 |
did things). Masking doesn't make foo-1.2::extras invisible, it just |
25 |
makes it visible but unusable. Even if you do take the "ignore masked |
26 |
things entirely" approach, the behaviour's highly weird when things |
27 |
like repository package.masks become involved -- I'm not sure you could |
28 |
define a consistent model that does 'the right thing' purely on |
29 |
overlays (although feel free to try...). |
30 |
|
31 |
> > There's a different way of looking at it that focuses more on the |
32 |
> > repository level view at [1]. |
33 |
> > |
34 |
> > [1]: |
35 |
> > http://ciaranm.wordpress.com/2009/04/16/distributed-distribution-development-and-why-git-and-or-funtoo-is-not-it/ |
36 |
> |
37 |
> Interesting read. Can you think of anything technical that would make |
38 |
> moving portage to this model impossible? |
39 |
|
40 |
Other than the usual problems with moving Portage to things? No. The |
41 |
multiple repository model works fine with Gentoo, and it's possible to |
42 |
set it up so that it looks to the user exactly like an overlay model |
43 |
except where ::repo deps are involved. |
44 |
|
45 |
-- |
46 |
Ciaran McCreesh |