Bug#535355: dpkg-dev: dpkg-gencontrol -DPackage=foo -pfoo fails if foo isn't in debian/control

2009-08-13 Thread Emilio Pozuelo Monfort
Hi Raphael, sorry for the delay.

Raphael Hertzog wrote:
 On Wed, 01 Jul 2009, Emilio Pozuelo Monfort wrote:
 I'm implementing automatic creation of debug packages, and to generate
 their binary control file I'm using dpkg-gencontrol. The debug package
 are not listed in debian/control, and thus when calling dpkg-gencontrol
 I get something like:

 $ dpkg-gencontrol -DPackage=foo -pfoo
 dpkg-gencontrol: error: package foo not in control info

 Since I'm adding the field Package: foo using -D, I'd expect that to
 work.

 What do you think? I'm willing to provide patches if you think this is
 or might be a good idea.
 
 I think this is crazy. The entry for package foo would be mostly empty anyway.

My idea was to fill it with several -D options. The source entries would be
inherited from the source stanza of the control file.

 I suggest you generate another file (copying it and extending it as
 required) and you use the -c option of dpkg-gencontrol to use that file
 instead of debian/control. That file can even be a temporary file outside
 of the source tree.

That sounds too hacky and I want to avoid it. Right now I'm facking it from
stdin but then I miss the source fields.

 Generating binary control files for non-referenced packages could be a new
 feature, but it would be a new option and would not be based on a hack
 like you suggest: dpkg-gencontrol --dynamic -pfoo.
 
 This would fail if the the package foo is listed in the control file.

That sounds good. It's similar to defining a new package with -D, so I'm happy
with it. It should work with more -D options defined for that new package.
Something like

dpkg-gencontrol --dynamic -pfoo -DSection=debug -DPriority=extra -Dblah -c
debian/control

 Would that really be useful compared to creating another control file
 dynamically ?

I think so :)

My use case is ddeb creation for packages not listed in debian/control, fwiw.

Thanks for your consideration,
Emilio



signature.asc
Description: OpenPGP digital signature


Bug#535355: dpkg-dev: dpkg-gencontrol -DPackage=foo -pfoo fails if foo isn't in debian/control

2009-07-15 Thread Raphael Hertzog
On Wed, 01 Jul 2009, Emilio Pozuelo Monfort wrote:
 I'm implementing automatic creation of debug packages, and to generate
 their binary control file I'm using dpkg-gencontrol. The debug package
 are not listed in debian/control, and thus when calling dpkg-gencontrol
 I get something like:
 
 $ dpkg-gencontrol -DPackage=foo -pfoo
 dpkg-gencontrol: error: package foo not in control info
 
 Since I'm adding the field Package: foo using -D, I'd expect that to
 work.
 
 What do you think? I'm willing to provide patches if you think this is
 or might be a good idea.

I think this is crazy. The entry for package foo would be mostly empty anyway.

I suggest you generate another file (copying it and extending it as
required) and you use the -c option of dpkg-gencontrol to use that file
instead of debian/control. That file can even be a temporary file outside
of the source tree.

Generating binary control files for non-referenced packages could be a new
feature, but it would be a new option and would not be based on a hack
like you suggest: dpkg-gencontrol --dynamic -pfoo.

This would fail if the the package foo is listed in the control file.

Would that really be useful compared to creating another control file
dynamically ?

Cheers,
-- 
Raphaël Hertzog

Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny :
http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/




--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#535355: dpkg-dev: dpkg-gencontrol -DPackage=foo -pfoo fails if foo isn't in debian/control

2009-07-01 Thread Emilio Pozuelo Monfort
Package: dpkg-dev
Version: 1.15.3
Severity: wishlist

Hiya,

I'm implementing automatic creation of debug packages, and to generate
their binary control file I'm using dpkg-gencontrol. The debug package
are not listed in debian/control, and thus when calling dpkg-gencontrol
I get something like:

$ dpkg-gencontrol -DPackage=foo -pfoo
dpkg-gencontrol: error: package foo not in control info

Since I'm adding the field Package: foo using -D, I'd expect that to
work.

What do you think? I'm willing to provide patches if you think this is
or might be a good idea.

Thanks,
Emilio


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dpkg-dev depends on:
ii  binutils  2.19.1-1   The GNU assembler, linker and bina
ii  bzip2 1.0.5-3high-quality block-sorting file co
ii  dpkg  1.15.3 Debian package management system
ii  libtimedate-perl  1.1600-9   Time and date functions for Perl
ii  lzma  4.43-14Compression method of 7z format in
ii  make  3.81-6 An utility for Directing compilati
ii  patch 2.5.9-5Apply a diff file to an original
ii  perl [perl5]  5.10.0-23  Larry Wall's Practical Extraction 
ii  perl-modules  5.10.0-23  Core Perl modules

Versions of packages dpkg-dev recommends:
ii  build-essential   11.4   Informational list of build-essent
ii  gcc [c-compiler]  4:4.3.3-9  The GNU C compiler
ii  gcc-4.1 [c-compiler]  4.1.2-26   The GNU C compiler
ii  gcc-4.3 [c-compiler]  4.3.3-13   The GNU C compiler
ii  gnupg 1.4.9-4GNU privacy guard - a free PGP rep
ii  gpgv  1.4.9-4GNU privacy guard - signature veri

Versions of packages dpkg-dev suggests:
ii  debian-keyring2009.05.28 GnuPG (and obsolete PGP) keys of D
ii  debian-maintainers1.61   GPG keys of Debian maintainers

-- no debconf information




-- 
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org