How to package ?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
Ive got a question how to do the following right:
Im working on a library package (fidoconf) which has some binarys. So i build
a libfidoconf0, libfidoconf0-dev and fidoconf-runtime Package. It depends on
libsmapi but this is not a problem, i build this package yesterday.
libsmapi and libfidoconf are part of the Husky-Project (a complete Fidonet
Software Suite). More than 90% of all Husky-Programs depends on fidoconf and
smapi.
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 ?
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.
What do you say ?
- --
bye
Joerg
GPG-Keyid: 0x1120D31B
Fingerprint: A3D2 83A4 535D A826 F2AA 4348 8BDD 849C 1120 D31B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7Qccbi92EnBEg0xsRAo5CAJ9mjvbcVTmxfve7cqfkdtr7GIekPACfYSA7
Jo8xAXFyAQoD/odIyZnuty0=
=weki
-----END PGP SIGNATURE-----
Reply to: