On 16 February 2016 at 10:02, James Bowlin <[email protected]> wrote: > On Tue, Feb 16, 2016 at 09:12 AM, Natanael Copa said: > >> > > With the shell script "applets" we have the problem that we get >> > > real files, "owned" by a package. This causes a conflict error >> > > when installing the package. Yes, the package manager can be told >> > > to accept overwrites of given files, however, you can not make it >> > > automagically restore the busybox applet when you remove the >> > > bloated version of it. >> > >> > i'm not against adding a dedicated applet here, but your use case >> > doesn't sound like a compelling reason. sounds more like bad >> > package management. >> >> Do you have a better suggestion on how package manager should solve >> it? update-alternatives? > > One solution would be to keep the shell script "applets" in their own > directory and symlink to them just like you symlink real bb applets > to /bin/busybox. After you run "busybox --install -s", then run > a script that creates symlinks to the scripts if the slot in /bin/ > is not already filled. Something like: > > for script in $(find $SCRIPT_DIR -type f); do > link=/bin/$(basename $script) > test -e $link || ln -s $script $link > done
Right, i was about to suggest the same: Have sh-applets in e.g. /usr/share/busybox/sh and have your package-manager "divert" them as you seem to do already (or just use u-a for the diversion part). cheers, _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
