-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, Jul 12, 2006 at 08:04:33PM +0200, Klaus Kaempf wrote:
Having each and every service seperated might not be wanted, because of complexity it will bring.
Define one pattern "DNS Server" and one "DHCP Server" and one "DNS & DHCP Server" requiring both.
Won't that result in too many choices? Too many choices might confuse people more then it helps them. With these two you already have three. Add e.g. Apache, postfix, MySQL and ssh and you have a multitude of choices.
e.g. every single one, every combination of two, of three, four five and six.
I would thing that on one side that abount of choices is good, on the other side it might become confusing and this is just for a few services.
Or am I missing something?
I think that what needs to happen is have at the top most used packages
but lower dependentcies being the lowest posible grouping to statisfy
requirements.
"DNS & DHCP Server"
"DNS Server"
"DHCP Server"
So if the top is checked it requires all, but it only DNS Server is check
a partial is somehow reflected in the top level but only the DNS Server is
the requirement marked. Also
"All Server"
"LAMP Server"
"Apache Server"
"MySQL Server"
"P Server"
"PHP"
"Perl"
"Python"
"LAPP Server"
"Apache Server"
"Postress Server"
"P Server"
"PHP"
"Perl"
"Python"
So both the above have a P Server Reguirement, Apache Requirement, but the
database is a seperate requirement that may be filled by what ever choice
of database/s that are wanted.
I hope this explains the idea I am tring to suggest.
- --
Boyd Gerber