Le 18 juin 2004, à 13:14, David R. Morrison a écrit :
As announced on Tuesday, I've started to enforce the new validation checkNot sure to fully understand what you mean here, but well I explain my problem:
related to BuildDependsOnly. I've gotten some complaints about it, so
perhaps we need to discuss the situation.
As Dan Macks has pointed out to me, our shared libraries policy does not
explicitly require BuildDependsOnly for packages containing headers, but
only for the package containing the "main" shared library symlink.
In the next version of cssed there will be optional and/or integrated plugins; for that to work, headers are constructed both in cssed and/or in cssed-xxx-plugin packages. There is also a version, where the plugins are integrated into cssed directly (one unique package). The cssed-xxx-plugin packages will Depends on cssed. At the moment, none of those packages has BuildDependsOnly tag, and none have shared librairies, just a monolithic build (no split). The plugin are dynamically loadable (modules) with a structure like the following one:
in /sw/include/cssed: header in sw/lib/cssed/plugins: la and so files
What happens if the packages should have a BUILDEPENDS tag? Or is it OK as is?
Michèle <http://micmacfr.homeunix.org>
PGP.sig
Description: =?ISO-8859-1?Q?Ceci_est_une_signature_=E9lectronique_PGP?=
