|| On Wed, 30 Jun 2004 13:19:26 +0200 (CEST)
|| Andreas Tille <tillea@rki.de> wrote:
at> On Wed, 30 Jun 2004, Jeroen van Wolffelaar wrote:
>> Policy says the Binary: header should list all packages that _could_ be
>> build (but not necessarily are, for example, the xfree86 source package
>> lists xserver-xfree86, but it isn't build on s390). So, you should make
>> the clean target to put in debian/control the union of packages that
>> are build across all archs with this meta-package, and then all is fine.
at> The problem is that the cdd-dev framework provides a common template for
at> a control file which might lead to completely different binary target
at> packages (for instance: med-bio, med-imaging, med-tools, ... for Debian-Med
at> but jr-toys, jr-art, ... etc for Debian-Junior). So it is either impossible
at> to insert the Binaries in advance or we have to find a completely different
at> way to build these meta packages which would reduce the flexibility we
at> wanted to gain.
Is not possible build the control file in configure target, before the build?
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
you the whole house."
Attachment:
pgptMMOcI5Tcf.pgp
Description: PGP signature