You can build it if you like, but there really is no point
for this package IMO. Eric's packages are reliable, and he
has already built one for that Slackware version and kernel.
Eric is on the Slackware core team, and he writes and keeps
a good number of the scripts updated. You will find his name
in the ChangeLogs and Release notes.
For my personal preference, if Slackware does not have an
official package, then I look to Eric's repository. If he
does not have it, then I build it myself. I don't use any
other Slackware packages. That is just my opinion, based
on the fact that no one else has shown me the excellence
and track record that Pat and Eric have shown.
For building packages you need a SlackBuild script. Eric
has created Alien's SlackBuild Toolkit
to help guys like
me create a SlackBuild script. It's a starting point, and
usually needs a little bit of editing. That's what I do,
and am prepared for every Tom, Dick and Harry to come out
of the woodwork and tell me their method, why it's better
than mine, or preferred by them.
That's the beauty of Linux ... choices, many choices.
Do you need the package from the SVN branch, or will
the stable one do for you? Just curious.
As for packages ... we can all do it differently.
I backup all the PCs on this LAN to my server every night,
so I build everything under my /home directory. I have a
directory named ~/build/ which holds all the subdirectories
of different software. I also have ~/kernel/ which holds
all the kernels I build. When one is obsolete, I will