Hi, Please find attached a new ebuild for Gnomad2, an interface to use your Zen/Jukebox Creative on Linux. It uses libusb and libnjb (just submitted the latter) as a dependency. You obviously have to have gnome2 core packages. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 12986 [details] gnomad2-2.0.2.ebuild (New Package)
Created attachment 13202 [details] gnomad2-2.0.2-r1 (fixed dependency issue)
Created attachment 13572 [details] gnomad2-2.0.2-r2.ebuild (bugfixed) This should hopefully be the last set of 2.0.2 which fixes a CFLAGS issue resulting in segfault when launching gnomad2.
Not all dependencies are in portage yet.
Created attachment 22551 [details] gnomad2-2.3.0 to match libnjb-1.0 release Here's the new ebuild for Gnomad2. It works with both libnjb-1 et libnjb-cvs Steph
Depends information is missing. It's dependencies are in portage however. Checking this ebuild out, mainly since you've actually been version bumping it despite no response :) Sorry for the delay. Other then that, seems to compile correctly. State of 2.4.0?
2.4.0 depends on libnjb-cvs which i submitted as bug #22489 but still not in portage. Also, seems that any gnomad2 app is gone from stable ? emerge -s gnomad2 Searching... [ Results for search key : gnomad2 ] [ Applications found : 0 ] Steph
libnjg-0.9, and 1.0 are currently masked in portage. For 2.4.0, I'm rather hesitant to be adding a cvs ebuild into portage for it; a snapshot is much more preferable. For gnomad2, not sure, although I do recall seeing open bugs regarding it.
This is someting i argued a bit against. We do have some CVS ebuilds, why can't we do it for libnjb too ? I'm one of the active members of the project and always working against CVS. Please find the 2.4.0 ebuild attached, using the libnjb-cvs for now. We are on the way to release the 1.0.2 build which will support gnomad 2.4.0 out of the box, i'll then commit a 2.4.0-r1 to this bug. Steph
We prefer not to use cvs ebuilds if there is a stable package available. It just doesn't make sense under most circumstances. If in your development, you prefer using ebuilds for updating from cvs, then by all means do so, but most perople prefer to keep their development and production binaries separate, and using cvs ebuilds breaks that. I'm looking at the 2.3.0 ebuild now...
2.3.0 is in portage...
Created attachment 26808 [details] gnomad2-2.4.2.ebuild Needs http://bugs.gentoo.org/show_bug.cgi?id=43675 to work properly or libnjb-cvs.
reopened for new version...
in portage
Created attachment 30515 [details] gnomad-2.4.4 ebuild new release
Created attachment 30516 [details] libnjb-1.1 new version of libnjb needed for gnomad-2.4.3/2.4.4
In the future, you should open a new bug report as most dev's don't check CLOSED/RESOLVED bugs for updates.
thanks, they've been added to portage.