net-p2p/limewire is masked due in part to availability of net-p2p/frostwire. However, if you run a stable system, frostwire is masked. So, if you delete limewire before trying frostwire, you don't have an easy way to install either of the apps. Shouldn't limewire be kept until frostwire is marked stable? Reproducible: Always Steps to Reproduce: 1.emerge frostwire 2. 3. Actual Results: momma@casper ~ $ emerge -pv frostwire These are the packages that would be merged, in order: Calculating dependencies / !!! All ebuilds that could satisfy "net-p2p/frostwire" have been masked. !!! One of the following masked packages is required to complete your request: - net-p2p/frostwire-4.13.5 (masked by: ~x86 keyword) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. Expected Results: frostwire should install. momma@casper ~ $ emerge -pv limewire These are the packages that would be merged, in order: Calculating dependencies | !!! All ebuilds that could satisfy "net-p2p/limewire" have been masked. !!! One of the following masked packages is required to complete your request: - net-p2p/limewire-4.12.6-r1 (masked by: package.mask) /usr/portage/profiles/package.mask: # William L. Thomson Jr. <wltjr@gentoo.org> (25 Mar 2008) # Masked due to bugs and availability of forked alternative Frostwire. # Which is more equivalent to Limewire Pro and has been added to portage. # This ebuild will be moved in 30 days to the java junkyard overlay. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook.
Limewire should never have been stabilized, and neither package runs as the binary from upstream. I just looked at the stable request, and I can't believe I filed that. You can still use it, but unmasking it locally if you wish. But any bugs filed, won't be worked, no support, etc. I could unmask but that would imply it's supported. I will consider removing mask, or maybe de-stabilizing the ebuild or something in the mean time that's a bit friendly. I just don't want to encourage use of that package anymore. I am surprised many can use it, and not sure how it got stabilized. I guess it's in a bit better shape than frostwire, since there was less damage I could do compiling from source :) I will see about working on the frostwire patch a bit more, but kinda lack time there. Not really a crucial app for me, and borderline illegal when I use it anyway :) Surely welcome any community contributions, as the package will need lots of work to open up a bit more, and use current system installed libraries etc. Along with unbundling the rest of the deps. So far seems most users are just that, which is fine. I just lack time, and when I have it, frostwire will get it. :)
For my two cents, on a stable AMD64 system just put together a week ago, Limewire works just fine, and always has worked just fine from the ebuilds in Gentoo for years (for me anyway, and on various platforms)... And frostwire involves a bunch of BS located in bug 215423. There should probably be a transition period in place, or at least have one or the other stable for the average user.
(In reply to comment #2) > For my two cents, on a stable AMD64 system just put together a week ago, > Limewire works just fine, and always has worked just fine from the ebuilds in > Gentoo for years (for me anyway, and on various platforms)... What version of java are you running it under? It get's problematic for me with >= 1.6. Also ever since I unbundled some of it's deps, it throws a bit more exceptions at runtime. Not seen unless you invoke it in a terminal. > And frostwire > involves a bunch of BS located in bug 215423. There should probably be a > transition period in place, or at least have one or the other stable for the > average user. Well it's about support. Granted limewire might work perfectly now for you and others. If/when it breaks there will be no support for it. This is all FOSS stuff, so if the community wants either stable. We all should collectively step up. There is nothing we can do for Limewire long term. I don't want to give off false future perceptions. Hate me today vs tomorrow :) Like for you it worked for years. If it is stable again and breaks. You or others will file bugs. Which at that point most all will not be happy with me when I say I won't work the bug. Or look into fixing Limewire. Close as wontfix, etc. Or when new versions are out, like now. Request it be bumped to current. Bottom line, there is no one to support the package. So while it might be stable now. Without someone including others in herds. Willing to step up and maintain, I am just trying to head off a future problem. Yes it's not ideal today, but hopefully tomorrow will. And we will have a stable FOSS version, vs a stable semi FOSS version with a unresponsive and MIA upstream. Plus one can still unmask Limewire and use it. Just not expect support if they have problems, or want to see it bumped.
For the record, forgot to mention. I have no plans to remove Limewire ATM. Just no plans to support or do anything for that package. Once Frostwire is unmasked and/or stable. Then and only then will I look to remove Limewire from portage.
I'm running 1.6.0_05, which is marked stable on AMD64. IMO if a program does not work at all under a completely stable build, it should probably be marked more than unstable, probably more like masked. A program marked unstable may have bugs, but it should at least start, yes? All the fixes on the forums just state that people are bypassing the ebuild altogether and installing from the Frostwire website. Anyway, more to the point, the reason I was distressed was this: # William L. Thomson Jr. <wltjr@gentoo.org> (25 Mar 2008) # Masked due to bugs and availability of forked alternative Frostwire. # Which is more equivalent to Limewire Pro and has been added to portage. # This ebuild will be moved in 30 days to the java junkyard overlay. Stating it will be removed in 30 days.
....which I now realize has already elapsed, but still.
Well it starts for me, otherwise I would not have committed it, and I would have masked it. Also there are suggestions on another bug as to how to replace just the two problematic files. Part of the reason for not masking, is so more people run into the issues. That I can't replicate. So maybe we can get someone to step up until I have more time for this. Which considering this is not an app I use to make $. Much less it's one that is borderline illegal for me and others to use. It's not a major priority to me ;) As for Limewire's p.mask. I updated the text last night, sync your tree and you will see. The 30 day thing is basically a default line of text we on the Java team include with most anything we mask for removal. Also at the time of masking, I had just merged Frostwire from ebuild successfully. Which is why I did not mask it, and before the bugs were reported. Had planned to remove it in 30 days. Things happened, plans changed, I updated mask to reflect that :) FYI, time spent commenting here, doesn't go to working on the ebuild. :(
Ok, just made an attempt to resolve the other bug. Pretty sure it should be resolved now. So pending any problems from here. We might be back on track to remove Limewire in ~30 days or so. Depending on if more bugs get filed for Frostwire, and if I want to look to stabilize it. Despite bundled deps.
(In reply to comment #8) > Ok, just made an attempt to resolve the other bug. Pretty sure it should be > resolved now. So pending any problems from here. We might be back on track to > remove Limewire in ~30 days or so. Depending on if more bugs get filed for > Frostwire, and if I want to look to stabilize it. Despite bundled deps. > Hi William; Frostwire works for me from the ebuild now (-r1 version). I just want to thank you for the work and time you spend developing for Gentoo. I don't know anything about about programming and hacking -- I'm just a user -- so there's not much I can do to help. But I just want you to know how much I appreciate your efforts. Thanks, Vicki
Thanks for the kind words, much appreciated. But even as user, there is lots of things that one can do. Never self impose limitations just because you feel you are a user, or lack skills. Never a better time to gain skills than the present. Plus us devs aren't really that special. We are human and do not posses super powers. Well maybe some due, but surely not I :) Not to mention just being a Gentoo user, puts you way ahead of most skill set wise! Really for most things it's just looking into details. You would be surprised how much those with no skills can help out. We all had no skills at one point wrt to computers. I strongly believe anyone with a will, can do anything wrt to computers. Some of it might be rocket science, but most is not. Not to long ago, almost 2 to 2.5 years ago. I was just a user like others. So anyone can be a user or a developer. It's all about will, ones' needs, etc. Also openness to learning new things, and ability to receive constructive criticism helps. Anyway thanks again for the kind words, sorry for any problems or headaches. Surely more join and pain to come :)
Reassigning to herd since wltjr has left Gentoo, bug #135927.
limewire no longer in the tree. Closing as won't fix
