On Thu, Oct 15, 2015 at 5:15 PM, Zac Medico <zmed...@gentoo.org> wrote: > On 10/15/2015 02:03 PM, Rich Freeman wrote: >> On Thu, Oct 15, 2015 at 4:57 PM, Zac Medico <zmed...@gentoo.org> wrote: >>> Given the goals, having catalyst seed /var/lib/portage/world seems >>> pretty reasonable to me. >> >> Then the question becomes how. Does it diff @profile between the two >> profiles and put the extra stuff in @selected? Or, does the profile >> just contain a special file containing the stuff that gets seeded? >> That is really the gist of the two approaches, and if you just have a >> special file full of stuff that gets seeded you really don't need >> another profile, which is nice since profiles are a PITA right now. >> > > We already have packages.build which is used to build stage1, so > introducing a packages.stage3 that's used to seed @selected (aka > /var/lib/portage/world) for stage3 seems reasonable.
Seems reasonable to me, and the nice thing is that it doesn't change the behavior of anything at all besides catalyst, so other than starting out with a non-empty /var/lib/portage/world users won't see a thing happen. I won't bikeshed on the name of the file. Whatever seems reasonable to the catalyst team works fine for me. This then conserves @profile for stuff that is more essential to the profile itself, such as a fancy firmware loader for an arm box or whatever (in our future luxury world where we can spare new profiles for specific boards and such). Of course, it wouldn't hurt to standardize on how such sets work if we're going to start using them seriously if that isn't in PMS. However, I see all of that as off-topic for the present discussion other than the desire to not interfere with it. -- Rich
