| 1 |
On Fri, 29 Jun 2007 05:07:28 +0200 |
| 2 |
Marius Mauch <genone@g.o> wrote: |
| 3 |
|
| 4 |
> Please reply on gentoo-portage-dev, _not_ on gentoo-dev, thanks. |
| 5 |
> |
| 6 |
> One missing feature in portage is the lack of package sets. Before we |
| 7 |
> (re)start working on that however I'd like to get some feedback about |
| 8 |
> what properties/features people would expect from portage package set |
| 9 |
> support. |
| 10 |
> Some key questions: |
| 11 |
> |
| 12 |
> - should they simply act like aliases for multiple packages? E.g. |
| 13 |
> should `emerge -C sets/kde` be equivalent to `emerge -C kdepkg1 |
| 14 |
> kdepkg2 kdepkg3 ...`? Or does the behavior need to be "smarter" in |
| 15 |
> some ways? |
| 16 |
> |
| 17 |
> - what kind of atoms should be supported in sets? Simple and versioned |
| 18 |
> atoms for sure, but what about complex atoms (use-conditional, any-of, |
| 19 |
> blockers)? |
| 20 |
> |
| 21 |
> - should sets be supported everywhere, or only in selected use cases? |
| 22 |
> (everywhere would include depstrings for example) |
| 23 |
> |
| 24 |
> - what use cases are there for package sets? Other than the |
| 25 |
> established "system" and "world", and the planned "all" and |
| 26 |
> "security" sets. |
| 27 |
> |
| 28 |
> - how/where should sets be stored/distributed? |
| 29 |
|
| 30 |
Forgot one question: |
| 31 |
|
| 32 |
- should sets have metadata? (e.g. a description for searching) |
| 33 |
|
| 34 |
There hasn't been much feedback yet, so if you want to add anything now |
| 35 |
is your chance, otherwise I'll implement things the way that works |
| 36 |
best/is easiest for me, which might be different from what you expect. |
| 37 |
|
| 38 |
Marius |
| 39 |
|
| 40 |
PS: I also accept off-list replies |
| 41 |
|
| 42 |
-- |
| 43 |
Public Key at http://www.genone.de/info/gpg-key.pub |
| 44 |
|
| 45 |
In the beginning, there was nothing. And God said, 'Let there be |
| 46 |
Light.' And there was still nothing, but you could see a bit better. |
Archives