From: Sebastian Pipping <webmaster@hartwork.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] overlay usage and maintainence [was: DistroWatch and Gentoo packages: status quo and future]
Date: Mon, 14 Sep 2009 20:28:26 +0200 [thread overview]
Message-ID: <4AAE8B4A.7080703@hartwork.org> (raw)
In-Reply-To: <20090914150543.395d347d@snowcone>
Ciaran McCreesh wrote:
> Because an overlay model has only a single foo-1.2. Think of it like
> stacks of paper. You've got your main repository:
>
> ::gentoo foo-1.1 foo-1.2 foo-1.3
>
> and on top of that you put your overlay:
>
> ::extras foo-1.2 foo-1.4
> ::gentoo foo-1.1 foo-1.2 foo-1.3
>
> and then looking down from the top, all an overlay model package
> manager sees is the foo-1.2 from the overlay. There's no
> foo-1.2::gentoo and foo-1.2::extras, there's just a single foo-1.2
> that's made from (gentoo + extras).
I see. So it would not work for dependencies but it should work for
masking. That alone wouldn't make me happy, though.
> There's a different way of looking at it that focuses more on the
> repository level view at [1].
>
> [1]: http://ciaranm.wordpress.com/2009/04/16/distributed-distribution-development-and-why-git-and-or-funtoo-is-not-it/
Interesting read. Can you think of anything technical that would make
moving portage to this model impossible?
Sebastian
next prev parent reply other threads:[~2009-09-14 18:28 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 23:02 [gentoo-dev] DistroWatch and Gentoo packages: status quo and future Sebastian Pipping
2009-09-12 2:24 ` [gentoo-dev] " Ryan Hill
2009-09-12 12:15 ` Sebastian Pipping
2009-09-14 2:46 ` Ryan Hill
2009-09-29 1:08 ` Donnie Berkholz
2009-09-12 4:48 ` [gentoo-dev] " Aaron Bauman
2009-09-12 17:26 ` Sebastian Pipping
2009-09-12 11:23 ` Marijn Schouten (hkBst)
2009-09-12 17:29 ` Sebastian Pipping
2009-09-13 9:11 ` Jesús Guerrero
2009-09-13 10:47 ` Richard Freeman
2009-09-13 10:57 ` Jesús Guerrero
2009-09-13 13:24 ` Richard Freeman
2009-09-13 19:39 ` Sebastian Pipping
2009-09-13 19:38 ` Sebastian Pipping
2009-09-13 11:30 ` [gentoo-dev] overlay usage and maintainence [was: DistroWatch and Gentoo packages: status quo and future] Thomas Sachau
2009-09-13 18:57 ` Patrick Lauer
2009-09-13 19:03 ` Jesús Guerrero
2009-09-13 19:41 ` Patrick Lauer
2009-09-13 20:04 ` Jesús Guerrero
2009-09-13 19:25 ` Alexander Færøy
2009-09-13 19:45 ` Sebastian Pipping
2009-09-13 20:00 ` Alexander Færøy
2009-09-13 20:02 ` Ciaran McCreesh
2009-09-13 20:17 ` Sebastian Pipping
2009-09-14 14:05 ` Ciaran McCreesh
2009-09-14 18:28 ` Sebastian Pipping [this message]
2009-09-14 18:51 ` Ciaran McCreesh
2009-09-14 22:03 ` Zac Medico
2009-09-16 20:31 ` Sebastian Pipping
2009-09-16 21:21 ` Zac Medico
2009-09-13 13:59 ` [gentoo-dev] Re: DistroWatch and Gentoo packages: status quo and future Duncan
2009-09-13 14:36 ` Dale
2009-09-13 15:05 ` Albert Hopkins
2009-09-13 15:45 ` Dale
2009-09-13 19:52 ` Sebastian Pipping
2009-09-13 21:25 ` Dale
2009-09-13 21:54 ` Alex Legler
2009-09-13 22:08 ` Dale
2009-09-13 22:53 ` Alex Legler
2009-09-13 23:06 ` Dale
2009-09-13 20:00 ` Sebastian Pipping
2009-09-20 19:12 ` Duncan
2009-09-21 2:10 ` Angelo Arrifano
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=4AAE8B4A.7080703@hartwork.org \
--to=webmaster@hartwork.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