Re: [proaudio] jackdmp build fails

[Thomas Kuther <gimpel@xxxxxxxxxxxxxxxx>]

On Sa, 03.05.08 11:05 Thomas Kuther <gimpel@xxxxxxxxxxxxxxxx> wrote:

> On Sa, 03.05.08 10:38 Geoff Beasley <songshop@xxxxxxxxxxxxxxx> wrote:
> 
> > g'day. 
> > emerging jackdmp-9999-r1 give the following error
> > 
> > >>> Install jackdmp-9999-r1 
> > into /var/tmp/portage/media-sound/jackdmp-9999-r1/image/ category
> > media-sound make: *** No rule to make target `install'.  Stop.
> >  * 
> >  * ERROR: media-sound/jackdmp-9999-r1 failed.
> >  * Call stack:
> >  *               ebuild.sh, line   49:  Called src_install
> >  *             environment, line 2365:  Called die
> >  * The specific snippet of code:
> >  *       make DESTDIR="${D}" datadir=/usr/share/doc install || die;
> >  *  The die message:
> >  *   (no error message)
> >  * 
> >  * If you need support, post the topmost build error, and the call
> > stack if relevant.
> >  * A complete build log is located 
> > at '/var/tmp/portage/media-sound/jackdmp-9999-r1/temp/build.log'.
> >  * The ebuild environment file is located 
> > at '/var/tmp/portage/media-sound/jackdmp-9999-r1/temp/environment'.
> > 
> 
> Uh, looking at that ebuild's pkg_postinst() and pkg_postrm(), it's
> really pure evil. This might work with portage, but not with paludis
> and such.
> 
> jackdmp drop-in replaces jack-audio-connection-kit, but as so many
> packages depend on it directly... what do you guys think would be the
> best solution to work around this.
> 
> One idea would be to add a jackdmp useflag to
> jack-audio-connection-kit ebuild, and if enabled, it does nothing
> else but pull in jackdmp as dependency - like acting as a virtual.
> 
> Opinions?

Well, said and done. Works fine for me so far.
This is for jackdmp-9999-r1 and jack-audio-connection-kit-9999 only so
far.

Please test! (Especially if the depency hell resolves correctly...)

Thanks,
Tom

Attachment: signature.asc
Description: PGP signature