ebuild in portage media-libs/lv2core-4.0 has SRC_URI which refers to non-existant file, the file that exists has .tar.bz2 extension and contents differ to that contained in gentoo mirrors Reproducible: Always Sorry if this is a confusing report but the ebuild in portage media-libs/lv2core-4.0 has in SRC_URI a file that doesn't exist upstream in http://lv2plug.in/spec/. There is in fact a file lv2core-4.0.tar.bz2 which differs in content to the lv2core-4.0.tar.gz stored in the Gentoo mirrors. Also lv2core-4.0 from the tar.bz2 installs a command line application lv2config and after there are new lv2 extensions installed this command should be ran to regenerate symlinks to the headers for applications to find and build against them. It looks like it could be done in pkg_postinst for these extensions but I'm really not too sure how this should be properly done and whether this violates some Gentoo policy by writing symlink files outside of the src_install. The lv2config command is not installed from the current ebuild in portage which references the tar.gz but is contained in the tar.bz2 hosted upstream. A related thing is the lv2 extensions what are located in the same URI in this report which a few sound applications are depending on, how is best that these ebuilds be added? I've created most of the ones that are considered "stable" in my local overlay by looking at the specs so far but consider this a request for guidance as lv2config should be ran in lv2core-4.0 too I think. I don't want to attach 5+ ebuilds to this report without the go ahead or commit them to pro-audio overlay duplicating work and wasting time. Sorry for the confusing nature of this report but I don't know how else this can be worked out than by asking for guidance on the matter and changing the lv2core in Gentoo. on the proaudio overlay list there are a few people asking about lv2core and the missing extensions so I hope this can be resolved somehow. Thanks.
yep; i had a quick look at the (new) lv2core which provides lv2config; we should move to this but first find a way to make it install its symlinks in ${D} rather than running it in pkg_postinst, so that the symlinks are removed when the package is uninstalled i didnt find any way to make it create its symlinks in $D with the current code, maybe we should patch it and send the changes back upstream. could you please post a link to your overlay ? since, after lv2config is sorted out, I plan to include the extensions in the portage tree (needed by new libs like lilv & friends)
Sorry for delay, I've uploaded my LV2 overlay here if you want to take a look: http://git.part17.co.uk/gitweb/?p=lv2-wip.git;a=summary I put lv2config in src_install and it seems possible to generate the symlinks with current lv2config in lv2core-4.0, I'm not sure the way I did it violates policy though. I copied the lv2core-4.0.ebuild from portage and added a call to lv2config to it along with the extensions. Some notes: Most extensions use waf but it seems a little faster to emerge and bloats the ebuilds less by not using it. I was tempted to inherit waf-utils but that requires EAPI=3 and lv2core is EAPI=2. Also all the waf wscript needed modifying to stop install of a .lock-wafbuild file so I just installed them all with a manual doins instead. I dumped them in media-libs but maybe there could be a better category. Maybe all these extensions could be bundled in to one package, I just noticed Debian has it this way, not sure how that would work though. Thanks for your advice.
from lv2core 6.0 release notes: This release simplifies how LV2 specifications are installed, so corresponding releases of all stable extensions at lv2plug.in have also been released, along with a new "urid" extension. There are no API changes in this release, but a few new properties have been defined (see below). Packaging Changes ----------------- The lv2config tool no longer exists. Specification packages simply install their headers to the appropriate locations. lv2core-6 is in tree, we dont need to mess with lv2config anymore -> fixed ¿?
Thanks :) I've updated my lv2 overlay with the newer extensions too.
Sorry didn't realise this was still open. Resolving as fixed. Thanks.
(In reply to comment #5) > Sorry didn't realise this was still open. Resolving as fixed. Thanks. extensions are provided by media-libs/lv2 now :)
