If anyone else is looking to use pacman for their LFS system, you can find my PKGBUILDs here. They're very bare at the moment and need to have dependency management added into them but even in their current state they've proven to be useful to me at least.

Feel free to contribute if you'd like. There's a tonne of packages left for which I'll need to create PKGBUILDs for (at some point I'll be compiling xorg and xfce) and I'll update the repo to add those as I get to them.

I currently use the Slackware pkgtools templates for building packages. The base is pretty much the same, but I have my own set of build flags tuned to my machine. I also split the contents of a package into libraries, binaries, configurations files, man & info pages, docs and with various dependencies enabled/disabled, a la Debian's packages. I use the CLFS book to build my system because LFS has almost always caused problems. I'm also on SysV init instead of Slackware's BSD init. Apart from dependency management, what advantages does the PKGBUILD system have over Slackware's? Doesn't the systemd policies that are integral to Arch make it cumbersome for an LFS build, or are you following the LFS systemd version?

I don't really know all too much about pkgtool to compare the pros and cons of it and pacman. I use pacman mostly because as a long time Arch user it's familiar to me and I'm comfortable with it. In saying that, what I do like about it is that PKGBUILDs are relatively simple to create, build flags can be set globally in the /etc/makepkg.conf file and I have the added benefit of being able easily modify and use PKGBUILDs for packages I want without necessarily having to do them all from scratch (though in my current set up that's exactly what I did).

As for my setup, it's pretty much a straight LFS build with a few minor modifications. I use systemd-boot over grub, plus a few over miscellaneous changes that I can't recall off the top of my head. I had been considering doing something with Runit or sinit, but I am also pretty familiar with systemd so I figured it'd be easier to stick with the devil you know and what not.

Have you made changes to the Pacman utility itself to adapt it to LFS?

Nah, I'm just using it as is. I am considering moving my various computers to LFS in which case I might set up a repo and make some customisations for that (but really it's just editing config files) so I only need to compile them once and then install the binaries elsewhere. To be honest, it's probably got a lot more capabilities than I need, but it does work which is all that matters in the end for me

Nice to see this.
I use pkgutils from CRUX and the PkgFiles are very similar to PKGBUILDS.
For pkgtools from slackware, you can add CruxPorts4Slack to your installation and make use of PkgFiles and PKGBUILDS to build a "Slackware" packages.

How/where did you add the package manager to LFS? I found out it can be done in ch5 at the end, you can even add it to a tools/ch5 tarball before starting ch6.
Another way is to use an existing install or livecd, create a small chroot with packages/binaries from slackware/crux/archlinux, ...
So many ways once you have some experience.

I also use pacman. I have installed the package abs (Arch Build System) from Arch to get easily access to all their PKGBUILDs. So instead of creating PKGBUILDs from scratch I always use theirs and just change everything that should be different on my system.

I have created some scripts that might be useful for you, or anyone using pacman. And of course for anyone else to study and get some ideas from. I have thought for quite some time now to upload them somewhere, but I haven't had the energy to do so. When I do, I'll start my own thread about it. But here's one to start with, to search for dependencies. http://pastebin.com/MfSp6JQG

Example output: