Peter wrote:
On 11/04/2006 01:32 AM, Kevin Walsh wrote:Grant <suppressed> wrote:To All: Please chime if you have an opinion one way or the other.My chime would be for you to add some sort of "kitchensink" USE flag, so that both bundles could be, err, bundled into one package. The installer can then decide how much of the bundle to use, by either making use of the USE flag or ignoring it. Gentoo is my distro of choice but, as I said, it's highly unlikely that I'd ever make use of a "www-apps/interchange" package. I would make use of a "dev-perl/BundleInterchange" package, as long as it just consisted of a list of dependencies. One other thing: You should add some sort of "are you nuts?" warning if the "ithreads" USE flag is found to be switched on when your "www-apps/interchange" ebuild is called. As you may know, Gentoo won't build Perl with threads enabled unless this USE flag has been specified. Gentoo describes the "ithreads" USE flag as "Enable Perl threads, has some compatibility problems." Your warning should probably be a little more descriptive than my suggested text. :-)I think it would be a good idea to have use flags for the various different dbs, or at least for the "big three", (MySQL, PostgreSQL and Oracle) which would require the additional DBD module and of course the database itself. I would recommend this for the www-apps/interchange package.
I doubt that requiring the database is a good idea. Connecting to a remote database server isn't an uncommon use case. Bye Racke -- LinuXia Systems => http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP => http://www.icdevgroup.org/ Interchange Development Team _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.