Quote:
...
It's the only package management tool I know of at present which allows one to manage source packages in the same manner as rpms.
Removal of a package is as easy as 'epkg -e <packagename>' to remove the package and its symlinks.
[/b]
|
Note that such systems (encap, autopackage, klik, or even building+installing from sources) are totally
not the same thing as RPMs.
Most specifically, you should know that when you use other package management backends on an RPM distribution (such as SUSE Linux, Fedora Core, etc...), none of them is aware of the other.
If you install a "package" with epkg, it
won't handle dependencies properly, as epkg is not aware of your RPM database. The opposite is true as well, unfortunately: if you have something installed with epkg, and some RPM requires that software, RPM will not be aware that you have it installed with encap.
encap/epkg might be more interesting than just building+installing from sources "manually", but that's it, it's totally not integrated nor aware of RPM, and you might end up with a big mess unless you really know what you are doing in the first place.
And while some users might think that RPM dependencies are a pain, it
is a good thing, really ;-)
Definitely would not recommend such an approach for anything but really experienced users.
Always try to install an RPM that has been built for your SUSE Linux version - if you can't find an RPM of some piece of software, contact me or the Packman team ;-)