Hi, What is the recommended way of creating the busybox-symlinks when there are conflicts?
I am currently deriving my own target from the "generic embedded" sample provided with T2. When simply and naively checking the "create busybox
symlinks" I run into duplicate file issues. > Found shared files with other packages: > bin/sh: bash busybox > sbin/ifdown: busybox rocknet > sbin/ifup: busybox rocknet > sbin/init: busybox minit > usr/bin/ar: binutils busybox > usr/bin/awk: busybox gawk > usr/bin/strings: binutils busybox > usr/bin/which: bash busybox > Found registered 'bad files' in package: > usr/bin/lpq: Only default printer may own this file > usr/bin/lpr: Only default printer may own this file > Due to previous errors. > --- BUILD ERROR --- So for every conflict I need to decide wether I want the regular or the busybox version. If it's busybox I want I can remove the regular package. Fine. If I want the regular version the standard way would be to exclude the command from the busybox-build. Hopefully the busybox-install will then not create the symlink. Right? How could I do that? Preferably in a target-specific way of course to not affect the rest of the T2 build. Alternatively I could create all the busybox-symlinks I want myself in the target-rootfs-skeleton that gets merged with the result from the package-builds. Propably using the #!ln-Notation. Lots of work that can of course be automated (although even having a list of the links this currently is a bit beyond my grasp of bash :-)). Ciao, MM -- Marian Aldenhövel, Rosenhain 23, 53123 Bonn http://www.marian-aldenhoevel.de "I ran some quick calculations on it. He's about 80% on the right track. That leaves him only 20% dead when he crashes." Bob C
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe t2
