Mats Kindahl wrote: > Hi guys! > > I've been running up against a problem when using MySQL, and that is > that there are no separation of packages for different roles. I think we > need four packages: > > drizzle-client: > Binaries for the clients that can connect to a Drizzle server > > drizzle-client-dev: > All header files and libraries needed to write a Drizzle client > > drizzle-server: > Binaries and libraries needed for running a Drizzle server > > drizzle-server-dev: > All header files, libraries, and other utilities needed to build a > plugin for a Drizzle server > > Of course we need a similar separation for Fedora, SuSE, etc.
Well... the separation is actually already there in the MySQL Debian packages. And although I agree in principal about what you are saying, the naming is a little different to meet debian standards. So we have: libdrizzle16 libdrizzle-dev drizzle-client drizzle-server (I've got prelimiary debs already... but I haven't touched them in a while because of the fast pace of change... but they'll be ready as soon as we need them) Open questions: 1) What should happen when someone says: apt-get install drizzle Should they get client and server? 2) How do we deal with plugin development? We could have, as Mats indicated, drizzle-server-dev. There is precedent for this with apache. This package would only install headers really though... although I guess that should be all you should need for plugin dev... > Ideally, the different distributions should be possible to build using > make by just doing something like: > > make dist-client > make dist-server > make dist-client-dev > make dist-server-dev > > ... which would then produce tar files for the different distributions. This would not be useful for Debian, as the debian package building system would not be able to take advantage of it. It would not, however, hurt anything. On the other hand, it may take some work to do. We are using the built-in make dist functionality from automake, and make dist doesn't work in subdirs... so someone would have to spend some time doing some serious make foo... might be fun though! > Then it is a simple matter of producing package files from each of them > (I could build some for Solaris, since I've done that already). I am firmly in favor of someone who is not me making Solaris packages. I am also in favor of someone who is not me making RPMs, although I will make them or help if need be. Monty _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
