Quote:
|
Originally Posted by "RobinVossen But, it doesn't have a Package manager. |
Oh! Not true!
It has a package manager, and a good one at that. It doesn't do dependency checking, so you have to think yourself. I have varying degree of success on that, but at least I know who to blame....

If I may give a piece of personalized advice --meaning this is not the advice I'd give everyone, but seeing as how you like compiling, command line, and the ease of the TUI I think you'll love this package manager-- you compile like this:
Code:
./configure && make && makepkg -flags packagename.tgz&& installpkg packagename.tgz.
i take it you understand all usual flags apply. So compile your package as you would on any system, adding the flags you want. Just never 'make install', but replace this with the 'makepkg' and 'installpkg' combo. It's gold. Why? You want to remove the package? removepkg! That's all there is to it. Want to try out a different compile of the same package?? Just add version numbers.
Safe all your active compiled packages in a special directory. /home/tgz/active/ or something like that. Now back that dir up as you do with every data dir. Want to reinstall? Move the packages from backup to the fresh system. And in one go, type:
Code:
installpkg /home/tgz/active/*tgz
All your home brew packages that you compiled just the way you want them are back in place.
Done
The one that downloads and checks dependencies is slapt-get.
There are also slackbuilds, which are essentially installers that you can add to uncompressed source and run the slackbuild instead of the regular compile steps.
And you can use cruxports. But I've never done that. It is suposed to be very good though.