Re: How to package ?
On Tue, Jul 03, 2001 at 03:22:35PM +0200, Joerg Jaspert wrote:
> Fidoconf is a central library in this Project, its the one used for the
> Config. Every Programm calls Fidoconf to get his configuration. All
> Configuration is done in one file (most of the time, 90%).
> So, my Problem:
> a.) One Binary (from 8) in fidoconf-runtime is really neccessary for
> libfidoconf (or better: for the User): You can check your config for Syntax
> Errors. But the other Binaries are just goodies. What should i do ? Put the
> one binary file in the dev-Package and let libfidoconf depend on it ? Or put
> it in the shared file (policy says no), or should libfidoconf depend on the
> runtime file ?
Checking for syntax errors doesn't sound really neccessary (e.g. you
could live without it if you have a known-to-be-good config file).
Leave it in the runtime package and put that package (without version
information) in the Recommends: of the shared library package. To
depend on it seems too strong.
Whatever you do, don't put binaries into the shared library package.
This prevents installation of multiple versions of the same library.
> There is another problem with the Configuration File for the Husky Suite. It
> is just one central Config for all Programs which comes with fidoconf and is
> in /etc/fido/config. It is not really policy-clean (every package should have
> its own subdir in /etc) but its the Husky-Way, only one central config for
> all programs.
> So i provide the Config (as an example, no debconf) in the Fidoconf Package.
> But where ? If i depend on the runtime-package i put it into the runtime. If
> not it is better to put it into the shared library package i think.
Put it into a husky-common package along with other stuff that is shared
among all of the Husky suite and let all Husky program packages depend
Andreas E. Bombe <email@example.com> DSA key 0x04880A44