On Friday 03 February 2006 22:00, MIkey wrote: > Each server type (web-servers, dns-servers, etc..) gets its own meta > package via the overlays that determines what apps are compiled.
I intended to do that - great idea and heads to a more standard set of server installs - that's certainly where I want to be > Got all that Yeah - that's fantastic, although one issue does remain... if you have 10 web servers, then they all use the same 'build profile' or whatever y ou called them, that's fantastic. However... what if on 2 of them, we want apache 'threads' enabled, and on 4 of them we want hardened PHP patches, but we don't want it on all of them due to some issue with the patch (this is all hypotetical). Lets also pretend that these 2 exceptions overlap, 1 threaded server, 1 threaded with hardened php, 3 hardened php, and 5 'standard' web servers. This means there's now 4 profiles, and 4 lots of build profiles to maintain, 99% of the packages in these build profiles will use identical use flags, only apache and php will be different - your system doens't allow for these exceptions very nearly, which is my biggest concern. I do entirly agree that standardisation is the way to go , but I want to be able to neatly handle the exceptions - because unfortunatly, they will happen. Many thanks for your reply, it's certainly food for thought. Kind Regards, Ian -- [email protected] mailing list
