[BusyBox 0004884]: Updates to dpkg

bugs at busybox.net bugs at busybox.net
Wed Sep 10 18:58:27 UTC 2008

A NOTE has been added to this issue. 
Reported By:                wz2b
Assigned To:                BusyBox
Project:                    BusyBox
Issue ID:                   4884
Category:                   Other
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     assigned
Date Submitted:             09-10-2008 07:55 PDT
Last Modified:              09-10-2008 11:58 PDT
Summary:                    Updates to dpkg
BusyBox's dpkg script handling is not exactly as specified in the Debian
Policy Manual.  One of the main differences is that busybox invokes the
scripts without arguments.  Even if BusyBox chose not to implement full
rewind capability, it would be helpful for scripts to be able to determine
why they are being called.

This is a significant job, and it is not necessary to replicate every
single thing that the policy manual demands.

First on my list of concerns is the fact that the 'postrm' script is only
called by BusyBox dpkg in the event of the package being purged.  What's
supposed to happen upon removal is: 1. "prerm remove"  2. remove all the
files except conffiles 3. "postrm remove" 4. remove scripts except
%s.postrm.  Then, if an actual purge was requested, postrm is called again
with the argument "purge."


 bernhardf - 09-10-08 11:58  
dpkg is about the biggest applet in busybox (that's a sad fact).
Even in its current state, there are numerous possibilities to shrink
busybox dpkg but there are very, very few people who are willing to bite
the bullet and start to actively care about it, at least in my

The alternative is of course to add a _carefully_ implemented ipkg to
busybox, which is imo a very worthwile goal but still needs alot of time
to do in a sensible and acceptable way.

Just to name another one, there is apkg which i know zilch about except
that i heared that it exists (so no, i do not recommend it since it is an
unknown beast -- at least unknown as far as i'm concerned, perhaps it's
cool, no idea).

Put short:
If you want to improve dpkg, then sure, please go ahead and submit
sensible patches that are tested and work fine. Short of implementing the
stuff you want yourself, shell out some money to somebody on the busybox
list to do the grunt work for you.
If _you_ were to add the desired functionality, then you should really
take it upon you to de-bloat the current dpkg that is in busybox as far as
you see fit.

Thanks for your suggestions and TIA for attaching sensible, tested patches
to add the functionality you seem to be lacking from the current impl of
dpkg in busybox.
regards etc,

Issue History 
Date Modified   Username       Field                    Change               
09-10-08 07:55  wz2b           New Issue                                    
09-10-08 07:55  wz2b           Status                   new => assigned     
09-10-08 07:55  wz2b           Assigned To               => BusyBox         
09-10-08 11:58  bernhardf      Note Added: 0011344                          

More information about the busybox-cvs mailing list