Shawn Walker wrote: > On Fri, Mar 21, 2008 at 6:18 PM, Jyri Virkki <[EMAIL PROTECTED]> wrote: > >> Danek Duvall wrote: >> Shawn Walker wrote: >> > >> > In my experience, a program often really needs postgres, MySQL, or >> > Oracle specifically. >> >> Well, having functional dependencies doesn't force them to be used >> inappropriately! >> >> If package foo depends specifically on Oracle, its dependency must >> call that out. You'd only declare a general "database" dependency for >> packages which work ok with any of them. >> > > I guess I'm just pointing out that I have yet to see a program that > can work with *any* database. > > That's why I've never liked "general" dependencies. > GlassFish Java EE 5 Application Server that includes the JPA layer for example. To be spec compliant GlassFish bundles Java DB (aka Derby) , but could use Postgres or MySQL or...
(In fact the thread was started based on my question regarding which dependency should I add to the GlassFish Application Server IPS packaging I am adding). Another example would be regarding JDK: Currently, Indiana IPS has JDK 1.6 but GlassFish can run with JDK 1.5 or JDK 1.6. If the IBM JDK or the BEA jRocket JVM would be part of IPS, how would I declare a JDK dependency (I would just need 1 installed)? A third example is around a Ruby and RubyOnRails Application. In theory, it could depend either on native Ruby system, or on a jRuby system that you deploy on top of the JVM... I am sure I am missing other examples. Ludo > Database probably isn't a great example though. > > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
