On 9/20/06, Danny van Dyk <[EMAIL PROTECTED]> wrote:
As long as we have no package sets support in portage, I do indeed think that this is the best way to go. Didn't realize that you mentioned it, too. @Stuart: What do you think?
Right now, I'm not too concerned about the lack of package set support. That might change down the road, after we've lived with it for awhile. One of the things we're going to trial is supporting USE flags in the seeds themselves. We'll try out having the seeds/lamp-server/release-1 profile (or whatever it ends up being called) setting a suitable set of USE flags to support a LAMP environment that includes Apache, PHP4&5, Perl, Python, and Rails. The seeds-base/lamp-server package itself will rely on USE flags to switch on all those options. If anyone wants to build the seed from source locally, they'll be able to change the USE flags (for example) to build a LAMP Server that's dedicated to just Rails, or just Python. We think that'll make the LAMP Server seed more useful to our users in practice. The folks who want a quick stage4 tarball to seed a box - they'll get the whole nine yards. But folks who want to customise things (by compiling from source, probably using a stage3 tarball and the standard minimal install CD) - they're catered for too. That's why - atm - we don't want to just lump everything into a profile, or just into a catalyst spec file. Maybe one of those will turn out to be the right way to go, but we'd like to explore this approach first, and see how things turn out. Best regards, Stu -- gentoo-dev@gentoo.org mailing list
