[Slackbuilds-users] nonstandard build scripts

B Watson yalhcru at gmail.com
Tue Aug 9 09:22:26 UTC 2011

On 8/9/11, Erik Hanson <erik at slackbuilds.org> wrote:
> I have a bit of a two-pronged question. Is there really that much code
> in drumkit2pkg that it can't be done in the SlackBuild itself?

Well, there's code in drumkit2pkg that's irrelevant to the SlackBuild: it
can wget the tarballs, and it can alter the drumkit.xml so that all the
hi-hat drums are in the same mute group (so that, if you've got an open
hi-hat hit, followed by a closed one, the open hit won't keep ringing out
over the closed hit. This is *essential* for realistic-sounding drums,
but I don't call this code from hydrogen-drumkits.SlackBuild).

The script actually tries to find the documentation within the
.h2drumkit tarball and place it in /usr/doc. It looks for demo-songs
within the tarball, places them where they belong (different dir from the
drumkits). It specifically looks for a drumkit.xml file (and refuses to
makepkg if it doesn't find it). It tries to handle incorrectly-packaged
drumkits (that don't contain a top-level directory within the tarball). If
you don't give it a slack-desc, it generates one... It basically tries
to be more generic than a regular SlackBuild would be.

> It looks like these h2drumkit files are just tarballs. What all do you
> have to do (besides unpack and place the files in the correct location)
> that, again, can't be done in the SlackBuild?

Nothing, I just don't want to rewrite the thing, is what this boils
down to... especially if I'm ever going to submit more drumkit packages
(in which case I'd have multiple copies of it, possibly different from
each other).

Eh, at this point, this thread now contains more text than the script
contains actual code, maybe I should have just STFU and submitted it.

More information about the SlackBuilds-users mailing list