| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 15/10/15 03:15 PM, Zac Medico wrote: |
| 5 |
> On 10/15/2015 08:34 AM, Mike Frysinger wrote: |
| 6 |
>> background: everyone wants @system to be slim, but most people |
| 7 |
>> want the initial stage tarball that we release and you install |
| 8 |
>> Gentoo from to not be completely sparse. we've got a bug for |
| 9 |
>> this topic: https://bugs.gentoo.org/393445 |
| 10 |
>> |
| 11 |
>> items to sort out: - should the list of packages be in catalyst |
| 12 |
>> or profile-stacked content -> imo it should be entirely in the |
| 13 |
>> profile |
| 14 |
>> |
| 15 |
>> - should the packages list be in a new packages.default, or |
| 16 |
>> should we create a new set to hold it, or should we just go |
| 17 |
>> with @profile ? -> @profile has the advantage of already |
| 18 |
>> existing. we have to be careful so as to make it difficult to |
| 19 |
>> uninstall packages that the user does not actually want. |
| 20 |
> |
| 21 |
> In portage, the current meaning of @profile is very similar to |
| 22 |
> @system, except that it implies that members specify dependencies |
| 23 |
> completely (allowing for optimal parallelization) [1]. The |
| 24 |
> @profile set is only enabled for profiles from repositories that |
| 25 |
> have "profile-formats = profile-set" set in metadata/layout.conf. |
| 26 |
> It's an extension which is not covered by PMS. |
| 27 |
> |
| 28 |
>> - if the packages aren't in @profile, should they be seeded in |
| 29 |
>> @world ? -> imo yes as we don't want all the default packages |
| 30 |
>> getting depcleaned as soon as you start using the new install. |
| 31 |
>> if they're in @profile, then this is a moot point (assuming |
| 32 |
>> depclean does not clean out @profile). |
| 33 |
> |
| 34 |
> In portage, @world = @profile + @selected + @system, which means |
| 35 |
> that @profile is protected from depclean since it's a part of |
| 36 |
> @world. |
| 37 |
> |
| 38 |
> [1] https://bugs.gentoo.org/show_bug.cgi?id=532224 |
| 39 |
> |
| 40 |
|
| 41 |
|
| 42 |
So just to clarify.. if we start adding these packages that are |
| 43 |
removed from @system into @profile, what do we gain here? They'll |
| 44 |
exist in the stage3's (which is one of the goals right?), and |
| 45 |
they'll be included in @world without entries in |
| 46 |
/var/lib/portage/world (so end-users will have them on their |
| 47 |
systems).. Seems like everything would be the same as if they were |
| 48 |
in @system, except 'emerge -e @system' wouldn't rebuild them..? Do |
| 49 |
we get the advantage(s) we were looking for, going this route? |
| 50 |
|
| 51 |
|
| 52 |
-----BEGIN PGP SIGNATURE----- |
| 53 |
Version: GnuPG v2 |
| 54 |
|
| 55 |
iF4EAREIAAYFAlYf/rUACgkQAJxUfCtlWe3dWQEAlo+oBK+uyzRf+fzF2o17skMS |
| 56 |
0438JShMlObzWOkgZYYA/R65hZUl7enVItRWvzqPSP0qfKLjmXjCWcJiuepBBoRl |
| 57 |
=1fJ6 |
| 58 |
-----END PGP SIGNATURE----- |
Archives