Carlo Calica wrote: > On 2/4/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: >> Hello all, >> >> Everything is fine, until the installer tries to perform some >> operation with symlinks, such as 'ln -s libc.so.6 libc.so'. Since >> libc.so already exists in /System/Index/lib and no '--force' flag was >> passed to ln, the link creation will fail, as well as the install >> procedure. >> > > How is this different from a normal "make install" on an other distro > where /lib/libc.so already exists (from an earlier version)?
Exactly, is there any difference? If not, then all "normal" distro's would have the same problem and then this is not a problem with the /S/I thing but with bad build systems that doesn't work if a previous installation already exists. I used to run Slackware before gobo, where everything was just installed right in /lib and /usr/lib, etc... And I can't remember having this problem ever. Isn't those symlinking stuff supposed to do ln -sf, or remove the old symlink before creating the new one? (If I remember correctly, unionfs allows one to "remove" files from the RO dir by adding 'blanks' in the RW dir, but perhaps this has to be enabled?) -- /Jonatan -=( http://kymatica.com )=- _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
