Baslinux mailing list

[3aoo-cvfd AT dea.spamcon.org]

James Miller wrote:
>
> But as you go further from that core and try to install other 
> components or applications, you should definitely expect to 
> encounter dependency problems.  

BasicLinux and Slackware 7.1 do not fix dependencies for you 
automatically.  They do not try to second-guess you.  If a 
particular package requires a library not on your system, it's 
up to you to install it.

> You'll have to resolve those yourself "manually" 

It's not that complicated.  ldd the binary and, if a library is 
missing, search for it in MANIFEST.gz.

Keep in mind that, after installing a few additional libraries, 
ldd will be less likely to show missing libraries in the future.
There are a few common libraries (eg. cxxlibs) that show up 
again and again.  Once you've installed those, dependencies are 
not such an issue.  If you are wondering why BasicLinux did not 
include all those libraries right from the beginning, the design 
philosophy of BasicLinux is to provide a small foundation (with 
a useful amount of functionality) that can be expanded using 
packages from Slackware.  It is NOT to guess what users might 
want to do and pre-install everything for them.

> But you'll be in for a big disappointment if you expect to 
> not have any dependency problems modifying a BL install.  

Modifying is not such a problem.  The tools are already there 
for editing scripts and changing the way BasicLinux works.  
Dependency problems only occur when you add pre-compiled 
binaries (particularly ones not from Slackware 7.1).

> you'll use "installpkg dependencyname" for the most part, 
> and maybe things like ldconfig as well 

installpkg (used for Slackware packages) does an automatic
ldconfig.  External libraries copied into the filesystem 
(without using installpkg or pkgtool) will need ldconfig.

Cheers,
Steven