Re: [gentoo-user] What to do if packages are old?
On 11/30/06, Hans de Hartog [EMAIL PROTECTED] wrote: Hi, I'm currently evaluating some exotic packages in the portage tree and found out that they're almost 2 years old, don't compile or crash immediately. When I go to their home page or forums, I see that lots of new versions have been released. What to do about this? I'm not going back to the early 90's to play around with tarballs, ./configure, make make install and after a few months end up in the hell of shared library dependencies and systems being polluted beyond repair. After all, that's why I've choosen Gentoo in the first place. Should I - kindly ask somebody to do something about it? - try to make an ebuild from a tarball? - something else? Thanks for your advice! Hans. -- gentoo-user@gentoo.org mailing list The s.o.p., I believe, is to check for bugs asking for new ebuilds, failing that, file one yourself, failing that, create an ebuild (probably using the old one as a guide), and submit it. If you get all the way to step 3, email me off list, I might be willing to help with some ebuild writing. You could also check and see if newer versions are keyword-masked or hard-masked, or see if they're in an overlay somewhere. Please correct if I'm wrong. -- Ryan W Sims -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] What to do if packages are old?
Hans de Hartog wrote: Hi, I'm currently evaluating some exotic packages in the portage tree and found out that they're almost 2 years old, don't compile or crash immediately. When I go to their home page or forums, I see that lots of new versions have been released. What to do about this? I'm not going back to the early 90's to play around with tarballs, ./configure, make make install and after a few months end up in the hell of shared library dependencies and systems being polluted beyond repair. After all, that's why I've choosen Gentoo in the first place. Should I - kindly ask somebody to do something about it? - try to make an ebuild from a tarball? - something else? Check bugzilla to see if there are version bumps + ebuild bugs in there already. Most of the time, maintainers leave, and the herds are left to take care of them. If no one in the herd is interested in the package, then things can stagnate. If there isn't a bug, feel free to file one. If you have some ebuild skillz and want to help maintain the ebuild, then let some developers know that you'd be willing to take care of the package. Or, look at project Sunrise as well. There's a lot of things that can be done, and I've just barely glossed over the basics. Most of the time it comes down to a per-package basis, and usually the case is that there's just no one interested in maintaining it. Steve -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] What to do if packages are old?
061130 Hans de Hartog wrote: I'm currently evaluating some exotic packages in the portage tree and found out that they're almost 2 years old, don't compile or crash immediately. When I go to their home or forums, I see that lots of new versions have been released. It would help if you listed the packages in question. -- ,, SUPPORT ___//___, Philip Webb : [EMAIL PROTECTED] ELECTRIC /] [] [] [] [] []| Centre for Urban Community Studies TRANSIT`-O--O---' University of Toronto -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] What to do if packages are old?
Philip Webb wrote: It would help if you listed the packages in question. Also thanks to Ryan and Steve to illustrate the situation in the not_so_common_packages scene. (BTW, how do I check for an overlay somewhere?) - freewheeling (dies in glibc with double free or corruption) In the tree is only 0.5_pre4 (masked ~x86). There's bug 149784 asking for a version bump to 0.5.2a and the newest version from the freewheeling people is 0.5.3 - sooperlooper (won't build at all) In the tree is only 1.0.3 (masked ~x86). No bugs reported. Latest version is 1.0.8c (and even 1.0.8u for the Mac). I guess I've to file a bug asking for a version bump? Hans. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] What to do if packages are old?
Hans de Hartog wrote: Philip Webb wrote: It would help if you listed the packages in question. Also thanks to Ryan and Steve to illustrate the situation in the not_so_common_packages scene. (BTW, how do I check for an overlay somewhere?) - freewheeling (dies in glibc with double free or corruption) In the tree is only 0.5_pre4 (masked ~x86). There's bug 149784 asking for a version bump to 0.5.2a and the newest version from the freewheeling people is 0.5.3 - sooperlooper (won't build at all) In the tree is only 1.0.3 (masked ~x86). No bugs reported. Latest version is 1.0.8c (and even 1.0.8u for the Mac). I guess I've to file a bug asking for a version bump? If you're going to file a stabilization bug, then make sure you do this: First, make sure the ebuild works and the program compiles cleanly without any problems. Make sure that all possible deps are stable for it (if they aren't file stable request bugs for those first). You can check the stable status by going to http://packages.gentoo.org/ and searching for the package in question. Then, when you file the bug, make sure you add the arches to the CC list so they get a copy. Oh yes, and don't file any stable request bugs unless the ebuild has been released for at least 30 days, and there are no bugs in bugzilla. That's a pretty hacked summary, again, but there ya go. :) Pretty much just make sure everything is good to go before filing a stable request. Doing the legwork really doesn't take much time, and it makes things much simpler for arch testers and developers. Steve -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] What to do if packages are old?
On 11/30/06, Hans de Hartog [EMAIL PROTECTED] wrote: Philip Webb wrote: It would help if you listed the packages in question. Also thanks to Ryan and Steve to illustrate the situation in the not_so_common_packages scene. (BTW, how do I check for an overlay somewhere?) [snip] The gentoo wiki I know has a semi-complete list, the forums discuss them, etc. Google is, as always, your friend. -- Ryan W Sims -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] What to do if packages are old?
On Thu, 30 Nov 2006 20:36:39 +0100, Hans de Hartog wrote: (BTW, how do I check for an overlay somewhere? emerge eix then run update-eix-remote update from cron.daily. Now eix will index all the overlays in layman. -- Neil Bothwick Sigh - An amplifier for people who suffer in silence signature.asc Description: PGP signature
Re: [gentoo-user] What to do if packages are old?
Selon Hans de Hartog [EMAIL PROTECTED]: Philip Webb wrote: It would help if you listed the packages in question. Also thanks to Ryan and Steve to illustrate the situation in the not_so_common_packages scene. (BTW, how do I check for an overlay somewhere?) - freewheeling (dies in glibc with double free or corruption) In the tree is only 0.5_pre4 (masked ~x86). There's bug 149784 asking for a version bump to 0.5.2a and the newest version from the freewheeling people is 0.5.3 - sooperlooper (won't build at all) In the tree is only 1.0.3 (masked ~x86). No bugs reported. Latest version is 1.0.8c (and even 1.0.8u for the Mac). I guess I've to file a bug asking for a version bump? Hans. -- gentoo-user@gentoo.org mailing list Add to the list above SNNS (Stuttgart Neural Network Simulator) which has been replaced for more than a year by JavaNNS. I use the tarball, as I don't know enough of gentoo package management to replace the first by the second. -- ~adj~ -- gentoo-user@gentoo.org mailing list
