Re: packages size versus files under dpkg control
On Thu, Sep 15, 2005 at 03:52:31PM -0400, Roberto C. Sanchez wrote:
> On Thu, Sep 15, 2005 at 01:37:27PM -0400, Justin Pryzby wrote:
> > On Thu, Sep 15, 2005 at 01:33:20PM -0400, Roberto C. Sanchez wrote:
> > > On Thu, Sep 15, 2005 at 05:30:30PM +0000, Thaddeus H. Black wrote:
> > > > W. Borgert wrote:
> > > > > Back to your question: I personally hate files that are not
> > > > > under dpkg control, because you cannot check using debsums,
> > > > > dpkg -L, dpkg -S, etc.
> > > >
> > > > This raises a topic I do not understand very well.
> > > > Since we are already on the topic, may I ask for further
> > > > advice?
> >
> > > Would there be a problem with shipping the package with a file of the
> > > same name and size 0, then have the postinst generate the file and
> > > replace the empty file with the new file? That also helps keeps things
> > > consistent as dpkg will automatically remove the generated file on
> > > package removal or purge.
> > MD5sum will be incorrect.
> > /var/lib/dpkg/info/*.md5sums
>
> An excellent point.
>
> Perhaps we can make use of some the recent research in the area of MD5
> collisions :-)
Only if you don't mind restricting yourself to files whose md5sum is:
d41d8cd98f00b204e9800998ecf8427e
:)
--
Clear skies,
> > Justin
Reply to: