On Fri, Apr 11, 2003 at 02:42:45PM +0200, Michael Banck wrote: > Other points about the above list: > - The adduser package had to be put explicitely into $required, because > hurd's postinst would fail otherwise: > /var/lib/dpkg/info/hurd.postinst: line 29: adduser: command not found > dpkg: error processing hurd (--configure): > subprocess post-installation script returned error exit status 127 > I'll file a bug about this, too. You probably need to get the required user/s put into base-passwd. > - aj: Would it make sense to split $required into $required and > $required_linux, for stuff like modutils, sysklogd? No. $required == stuff without which the system basically won't work; $base == stuff that's needed to be installed by default. If there's stuff that's only appropriate for some architectures, then it should get added to $required in an "if" (like happens for the different architectures now). > + required="$required libc0.3 hurd libncursesw5 adduser" > +# required="$(without_package "bsdutils" "$required")" > + required="$(without_package "login" "$required")" A for loop would probably be simpler: required="$required libc0.3 ..." for x in bsdutils login ...; do required="$(without_package "$x" "$required")" done > + for i in S 0 1 2 3 4 5 6; do mkdir -p $TARGET/etc/rc$i.d; done Should be done in whatever sysvinit package hurd uses. Cheers, aj -- Anthony Towns <email@example.com> <http://azure.humbug.org.au/~aj/> I don't speak for anyone save myself. GPG signed mail preferred. ``Dear Anthony Towns: [...] Congratulations -- you are now certified as a Red Hat Certified Engineer!''
Description: PGP signature