I think we agree that the last state of the server profiles was not useful. So let's discuss what would be useful. For the medium-term future, not for this current step now.
> > Err, ok, so now guys, we 're offering a base profile* with dri, cups, gmp, > fortran and pppd(?) enabled, at the same time openmp enabled but threads > disabled, no sockets, no caps no apache2 or mysql that I would probably > want if I wanted to build a server box etc. and we officially drop the > server profiles (which is true, they're unmaintained for ages). > my 2ct: * dri and cups should probably be moved to desktop profile * pppd is a local useflag and should be enabled by default in the capi ebuild * for apache2 and mysql see below, should be off imho even in a server profile... * caps should be discussed in a wider context (portage) > > Many have said that a "server" is something very generic, so is > "desktop". I think profiles were invented to make things easier and > safer for users, so now we 're doing it for "desktop" users but people > who want to build a server box have to scratch their heads from the > first moment. I'm fine with that if our community is fine with that. > Sure a server is something generic, too. However, since you mentioned mysql above, how about a postgres server? Or a web server using a daemon different from apache? :) This is why I think (as others) a server profile should basically be the same as a minimal profile. And then, defining a minimal profile separate from the base profile does not make too much sense. Rather, carefully try to move all specific stuff out of the base profile. [ That said, CVS is such a pain, I'll not do anything like this again before we finish the GIT migration... :D ] -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/
signature.asc
Description: This is a digitally signed message part.
