Bugzilla Bug 20925

Tested on x86, but should work on PPC too if Allegro support is not requested
(see below).

Notes on this ebuild:

DUMB consists of two parts: a core library that can generate music data and
doesn't depend on Allegro, and an Allegro interface library that provides a
convenient API for playing music through Allegro's sound system (amongst other
things). The majority of users will want both installed. However, currently the
ebuild will only install the core unless you use:

USE=allegro emerge dumb-0.9.2.ebuild

Should this be changed, i.e. should the ebuild be set up to build Allegro in all
cases? Note that I will be submitting a DUMB-XMMS ebuild shortly, and this will
depend on DUMB but won't depend on Allegro - and building Allegro takes a long time.

DUMB has a custom licence, which has changed since the last version. I will be
attaching the new licence file to this bug.

I get the impression writing the ChangeLog entry isn't my job, so I'll leave
that to whoever.

I'd like to be informed of the status of this ebuild, but there isn't a CC box
in this form. entheh@users.sf.net

Thanks. :)

Reproducible: Always
Steps to Reproduce:

Created an attachment (id=11884) [details]
ebuild for DUMB v0.9.2

The developers may want to tweak this file; see comments on the bug.

Oh, forgot to mention: this bug goes in media-libs/dumb.

Created an attachment (id=11887) [details]
Licence for DUMB v0.9.2

Doesn't quite match the licence.txt file in the release; I added a comment that
one of the points had been renounced. This is confirmed on DUMB's official
site, http://dumb.sf.net/ . Thus the licence is GPL-compatible. I don't know
how watertight this is legally, but Debian were happy with this, so ... and I
promise I won't sue you. ;)

Oh, and I found the CC box after I submitted the bug. So no problems there. :)

Created an attachment (id=11898) [details]
ebuild for DUMB v0.9.2

Oops: IUSE was not set correctly.

A further note though: the 'allegro' variable isn't listed in the list of USE
variables. Does any special action need to be taken to get it listed?

If it's a USE flag only used by a single ebuild, we can just use a local USE
flag that goes into use.local.desc.

done :) thanks for the ebuild, and sorry it took so long.

I just did an 'emerge sync' and an 'emerge search dumb', and only DUMB v0.9.1
came up (no DUMB-XMMS). I have ACCEPT_KEYWORDS="~x86". Sure enough,
/usr/portage/media-libs/dumb/ only contains the 0.9.1 ebuild. Was it supposed
to appear yet?

Thanks

nope, it takes about 30 minutes for stuff to filter through to the rsync
machine from the cvs tree.

cheers,

rob