keep-5-6-sep going in Monday'ish
tush at yahoo.com
Sat May 18 19:08:44 PDT 2002
Gerard Beekmans wrote:
>On Sat, May 18, 2002 at 09:30:57PM -0400, Gerard Beekmans wrote:
>>The easiest way around this is by creating symlinks to satisfy such
>>dependencies but we don't want to pollute the LFS directory structure so
>>I'd say create symlinks that are needed during a package installation, but
>>then remove them as soon as we're done installing the package. It's a
>>little bit extra work but I like it better that way.
>Then there are configure scripts that need the /bin/sh symlink.
>Contineously creating and removing it is a bit of a pain unless we decide
>to install bash right after Glibc and GCC?
>In light of this perhaps just create all symlinks that we need and just
>remove them prior to running 'make install' on a package that installs the
>real (dynamically linked) file.
>A mix of both? Create symlinks of often reoccuring dependencies and just
>create&remove ones that are only needed once or twice throughout chapter 6
>(such as cpp, pwd /dev/null perhaps others)?
My vote would be for creating the symlink when first required and
removing just before running make install for the package that installs
the real file.
The advantage is that we create only once and remove only once and
easier to implement.
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message
More information about the lfs-dev