Using the Slackware Package Manager in LFS?
 

I started building LFS over again, my last LFS attempt ended in failure (when trying to do a major GNOME version jump from 2.14 to 2.18), and decided that the next time I install LFS, I'll need a package manager. Even though, ordinarily I like to keep the package management in my head, but that's a bit difficult.

I ruled out portage, because, well Gentoo still works. :)

I thought about using dpkg (debian style package management), but decided against that.

Then I thought, what about the default package manager you get when you do a vanilla installation of Slackware off the CD?

Is there any helpful information concerning this? Like the name of the package manager, the source code, the dependencies, and how to package everything up?

It's been so long since I last used Slackware, that I forgot what it is, and I think googling "slackware package manager" would give me a whole lot of useless results, considering I hear there's a few types of slackware package management available.

Thanks in advance.

If I'm not mistaken, LFS includes the encap package management tool. Here are a couple of articles to read about it:
http://www.linuxfromscratch.org/hint...iles/encap.txt
http://www.linuxjournal.com/article/6694

I use it in SuSE on the rare occasion that I want to install something from source.

While it may be alright for you, but I don't want to create thousands and thousands of symlinks. :)

Maybe paco instead. It was originally written as a package manager for LFS: http://paco.sourceforge.net/

I think I got pkgtools working... Somewhat. I meant to edit my earlier post, but I forgot.

Even if it doesn't work, I have the original temp toolchain that I compiled packed in to a tar.bz2 file, I can always start over and try something else.

Look at this thread. It may be what you want:

uupt -- slackware's pkgtool, easily packaged even for you crazy LFS users

I've not used this, or even started my LFS build yet, but your questions triggered a memory, so I thought I'd post.

Regards,

-Drew

Nevermind, fixed it on my own. Turns out I had the wrong setting for KEYMAP. The issue has been resolved.