Limewire is up to version 4.14.1 with numerous bug fixes since the version in portage right now. Reproducible: Always I was able to produce a working ebuild, but I am sure that it needs some tweaking.
Created attachment 126977 [details] ebuild Tested on my amd64 box and it seems to work fine. There are a bunch of errors dumped to the console when running though.
polite bump
and another...
Just a FYI, if you rename the ebuild I've attached here to version 4.14.10. You can grab the LimeWireOther.zip from limewire.com and manually place it in distfiles. It will build and work fine. I just tested it on my P4 and AMD64 boxes with success.
Java, any interest in this?
I took over maintenance of Limewire a while back. I have tried to updated it and unbundle third party libraries and etc they are shipping with the binary version. There is a version from source in java-exp. Compiles, install, and some what runs, but can't figure out what asm library they were using or etc. So lots of exceptions and no usable at all. They don't provide any means to build limewire or create the resulting jars. I am having to do that manually and it's not coming along well. They seem to modify third party stuff, but not all those modifications or etc are available in source. Thus I have no clue what version of asm or etc I need to resolve the present exception issue. I have tried each version in tree, per it's slots, and nada. They don't tag releases or source releases with versions. So that makes mirroring that stuff very difficult when it comes time for a new version out there. I joined their -dev ml a while back, and it's the deadest list I have ever seen. 0 activity. Really about to give up on Limewire and look to Frostwire which is 100% open source. But that upstream refuses to package and release a source bundle at this time. Doesn't help this situation at all. So till both upstreams stop sucking, I am pretty much over it all. Will poke at it when I can. But not to confident progress will be made. More than likely Limewire will get set aside for Frostwire. Once I can get a versioned source release for Frostwire.
I'd say continue with bundled stuff meanwhile, as there seems to be user interest.
Even with bundled upstream binaries and source releases aren't versioned. That's a pita to deal with. I have no hope that contacting them would change that. Plus seems like there is just as much user interest in Frostwire. Need to comment on a forum post about making sources available. They were concerned on bandwidth, but don't seem to get that we mirror sources.
Been in contact with Frostwire upstream about source release. I will package Frostwire once a source package is available. Once that's done will likely remove Limewire from tree and move on. I would suggest anyone following this bug, also take a look at bug 187835. Once Frostwire is package, I will likely close this bug as wontfix. So pre-warning there. All should be just as pleased to use Frostwire in place of Limewire. So shouldn't be a big deal to remove Limewire once Frostwire is available.
(In reply to comment #9) > I would suggest anyone following this bug, also take a look at bug 187835. Which is this bug :) I meant bug 135144. Sorry for the spam.
I just added Frostwire to portage. As such I will no longer be supporting or maintaining Limewire on Gentoo. I will be package masking limewire in a bit, and removing from tree entirely after 30 days. Frostwire is more equivalent to Limewire Pro which was never in tree. So this isn't just a sideways move, it's a move up a bit as well :)
*** Bug 231523 has been marked as a duplicate of this bug. ***
Reassigning to herd since wltjr has left Gentoo, bug #135927.
Created attachment 238195 [details] Updated ebuild.
LimiWire is no longer in the tree. Closing as won't fix
