what are libraries?

[reed9]

thanks for those info.

would it also cause a conflict if i have installed a software and that this software had its own library with it in the rpm package. yet there are already available libraries for it?


sorry. really newbie here.
haven't even got to the point where I've installed a software yet.

This is part of why you should always install software using your package manager. The package format, such as rpm or deb, contains information on which libraries a program depends upon, and will automatically pull in those libraries when you install. (Assuming you have an internet connection.) Like Hazel said, in Windows, each program can have their own versions of these common routines, and they all have to load up, which isn't very efficient. In linux, programs share libraries and it is more efficient. The downside, though, is that programs are not bundled in self-sufficient packages, so if you don't have internet connection, installing new software can be a huge hassle as you hunt down all the dependencies and dependencies of dependencies to be able to install. Or if you use Slackware, whose default package manager does not do automatic dependency resolution. Though some people like that because it gives them more control.

Anyway, part of what a linux distribution does, is maintain a collection of packages that all work together. They make sure that all the appropriate libraries and dependencies of various programs are in their repositories, and that they all play nice together. Obviously, bugs and conflicts do occur, though. Part of why a distro like Red Hat is considered so stable, indeed, is so stable, is that it uses older packages that are very well tested, keeping bugs to a minimum. The downside is that you have limited access to new technology and software. Whereas Fedora not only comes out with a new version approximately every 6 months, but are known for including extremely up-to-date packages, meaning less testing and higher potential for bugs and complications. On the other hand, it can be nice to have access to newer software, especially if a feature has been added to a recent release that you really want.

Or you have a distro like Arch linux, which is "rolling release", meaning they are constantly updating the software in their repos, and usually new packages are available within days of a release. Sometimes sooner. KDE 4.2 was in the repos before the official release announcement, and KDE 4.3 within a couple of hours of the release announcement, I believe. You always have access to the most current stable releases of software, but you have to constantly be on your toes in case something breaks.

To sum up and answer your question, if you install rpms built for the correct version of your distro, using your package manager, then you should not have to worry about libraries. The distro maintainers have taken care of that for you. If you're wanting to install weird, obscure, or unmaintained software, you may run into problems.

[i92guboj]

There are safe ways to install software outside your package manager. You just have to be careful with the prefix(es) where you install your stuff manually. Usually, your home directory or under /usr/local are good places.

However you can always build your own packages as well. But a package can be as crappy and dangerous as a manual compilation if the builder has no idea of what s/he's doing. Of course, breakage is extremely rare when you use only packages that are official part of your distribution, at least for most distros.

[enhu]

thanks guys. i for got to reply as i got busy learning linux system. file system confuses me and so i tried understanding it first till this libraries. and i think i now know.

install software using yast or package manager is better than what idid before

thanks for the replies.