| 1 |
On Fri, 2007-06-29 at 05:07 +0200, Marius Mauch wrote: |
| 2 |
> Please reply on gentoo-portage-dev, _not_ on gentoo-dev, thanks. |
| 3 |
> |
| 4 |
> One missing feature in portage is the lack of package sets. Before we |
| 5 |
> (re)start working on that however I'd like to get some feedback about |
| 6 |
> what properties/features people would expect from portage package set |
| 7 |
> support. |
| 8 |
> Some key questions: |
| 9 |
> |
| 10 |
> - should they simply act like aliases for multiple packages? E.g. |
| 11 |
> should `emerge -C sets/kde` be equivalent to `emerge -C kdepkg1 kdepkg2 |
| 12 |
> kdepkg3 ...`? Or does the behavior need to be "smarter" in some ways? |
| 13 |
|
| 14 |
I like the alias way acting simply as a metapkg. |
| 15 |
|
| 16 |
> - what kind of atoms should be supported in sets? Simple and versioned |
| 17 |
> atoms for sure, but what about complex atoms (use-conditional, any-of, |
| 18 |
> blockers)? |
| 19 |
|
| 20 |
Mixed feelings about this. At first I assumed the syntax would be that |
| 21 |
pretty much of package.mask etc.. But I can for sure see the advantage |
| 22 |
of something as tad more complex of use conditionals being handy. |
| 23 |
USE="foo bar -nls" ROOT=/baz emerge sets/livecd. |
| 24 |
with the file being defined as nls? ( dislike/gettext ) but at the same |
| 25 |
time this is probably when we should use a proper ebuild as a metapkg. |
| 26 |
|
| 27 |
> - should sets be supported everywhere, or only in selected use cases? |
| 28 |
> (everywhere would include depstrings for example) |
| 29 |
|
| 30 |
Please NO. emerge.py should know about sets but ebuild.py should be |
| 31 |
oblivious to them. package sets as you are proposing imo should be |
| 32 |
limited to portage only. By putting package sets in ebuild depstrings we |
| 33 |
would be effectively forcing all other pkg managers to support the |
| 34 |
feature. I don't think we should do that. |
| 35 |
|
| 36 |
|
| 37 |
> - what use cases are there for package sets? Other than the established |
| 38 |
> "system" and "world", and the planned "all" and "security" sets. |
| 39 |
|
| 40 |
Assuming you guys run with with the simple alias method I don't see how |
| 41 |
'security' can fit into this. |
| 42 |
|
| 43 |
|
| 44 |
> - how/where should sets be stored/distributed? |
| 45 |
> |
| 46 |
> Please reply on gentoo-portage-dev, _not_ on gentoo-dev, thanks. |
| 47 |
> |
| 48 |
> Marius |
| 49 |
> |
| 50 |
|
| 51 |
-- |
| 52 |
gentoo-portage-dev@g.o mailing list |
Archives