Hi list, I'm packaging mysql-4.0.17 (without server) for dependency to various packages that I'll support, ie. mod_auth_mysql for the mysql based HTTP basic authentication for Apache and the new PHP module.
Now I get into a question: According how maintainers do, it seems that libraries, header files and base client programs are packages as "foobar-devel" with the same version-revision tagging. Unfortunatly this is mileading to the things reflected in the http://cygwin.com/setup.html page, where such a package is about to be named "libfoobar". So can we have a discurs on how a unique naming scheme can be entitled?! Should the mysql client programs, libraries and headers be named "mysql-devel" or "libmysql"? BTW, this one was build with a modified generic-build-script (yes, I took the note cerious that it is not a generic one ;). But I don't see actually how I can make the libraries build dynamically too. Currently I do build them pure statically and afterwards use a "mkdll.sh" script (should be known on the list) to produce the shared DLLs and the import libraries. Is there a more convinient way to do this using the generic-build-script directlty? Stipe mailto:[EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG M�nsterstr. 248 40470 D�sseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ ------------------------------------------------------------------- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -----END PGP PUBLIC KEY BLOCK-----
