Johny Mattsson wrote:
Maybe it would be useful to have a dummy DATABASE milestone, since I
imagine there are many applications that do depends on various databases
(mail & webservers being the first to come to mind). Having a DATABASE
milestone would allow for good decoupling between the individual apps
and the various databases. Databases would "BEFORE: DATABASE", and apps
depending on them could simply "REQUIRE: DATABASE" and not have to worry
about whether it was compiled with a postgresql, mysql or someothersql
database.
Just a thought, and possibly not the most well-considered one at that,
but I figured it might be worthwhile enough to share :)
This idea has been discussed in the past, and it has a lot of merit. I tend
to have a fundamental opposition to adding new pseudo-targets unless they
are ABSOLUTELY necessary, since they add complexity to the system and reduce
flexibility with ordering. However, this may actually be a case where it's
both useful and worth the cost.
I'm not going to take the initiative on this however, since I don't feel
that I understand all the issues well enough. If you (or anyone else) want
to pursue this, freebsd-rc@ is probably the place to start, then get
involvement from -ports once the pros and cons have been well discussed.
hth,
Doug
--
This .signature sanitized for your protection
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
