Hi! On Sun, 30 Jun 1996, Christian Hudon wrote: > On Sun, 30 Jun 1996, Andy Heroff wrote: > > Now, while configuring stuff, I ran into about 4 packages, including > > kernal-image-2.0.0-0, that complained that while running --configure or > > whatever, that it couldn't find a directory or file. I included the latter > > because it said in the package selection option that it was required. Is > > this true? And is there any reason in particular that dpkg is having > > problems finding the right directories? I know I wasn't very descriptve of > > the problem, but as none of the packages are that important to me to get > > installed (except for kernal-image?) I didn't write down every single > > message thrown at me. > > Just guessing wildly, make sure you have /bin/perl as a symlink pointing to > /usr/bin/perl... It's a known problem with the Perl package in 1.1. There > should be a new perl package in 1.1-fixes fixing this. Or you can just make > the symlink yourself.(If you want more than wild guesses, you really must > provide more info.)
Of course, making a symlink is the easiest way to solve this problem, but wouldn't it be better if the installation scripts, that depend on /bin/perl, were changed to reference /usr/bin/perl? IMHO, we would someone need to have perl in /bin, if it is symlinked to /usr/bin/perl and therefore *ONLY* available, if /usr is mounted? And /bin should only contain "Essential user command binaries". Thanks Chris
