Re: Keeping information on the build system
On Mon, Oct 15, 2001 at 10:19:17PM +0200, Cyrille Chepelov wrote:
> rationale: the buildinfo file is cool and nice ; but does it really have its
> place on the live file system ? (I'm not thinking big modern development
> machines which don't run ext2fs nowadays, but basic single-task junkware
> recycled PCs).
Hm. That's a point.
> Wouldn't it be more reasonible to have this file somehow "concealed" in the
> .deb binary package, and be extracted only on request (yes, this requires to
> keep the binary around, even after installing it, if you want to keep the
> option of reading that information afterwards and the system is not
> regularly updated).
> Alternatively, couldn't this information be collapsed into special-purpose,
> generated control fields, with some facility to let dpkg filter that out of
> available on systems which don't need to keep that information around ?
If we must modify dpkg anyway, why not add this sort of info in a way
similar to package signatures ? Signing a deb twice gives me:
$ ar tv comerr-dev_2.0-1.25-1_i386.deb
rw-r--r-- 0/0 4 Sep 22 17:16 2001 debian-binary
rw-r--r-- 0/0 1611 Sep 22 17:16 2001 control.tar.gz
rw-r--r-- 0/0 37449 Sep 22 17:16 2001 data.tar.gz
rw-r--r-- 1000/100 72 Oct 16 10:06 2001 _gpgfoo
rw-r--r-- 1000/100 72 Oct 16 10:06 2001 _gpgbar
I don't really know the internals of the thing, but a quick test tends
to show that adding a "buildinfo" component with "ar q" does not
interfere with normal operation (dpkg: -i -I -c, debsigs).
Yann Dirson <firstname.lastname@example.org> | Why make M$-Bill richer & richer ?
Debian-related: <email@example.com> | Support Debian GNU/Linux:
Pro: <firstname.lastname@example.org> | Freedom, Power, Stability, Gratuity
http://ydirson.free.fr/ | Check <http://www.debian.org/>