There are some updated unmaintained packages on http://www.maol.ch/crux/ [root@mob:~]# prt-get dup [...] I'll remove them from my repo as soon as there's an updated version in unmaintained. Which makes me wonder whether we should define update procedures for unmaintained, like "execute 'diff -u ...' from /" or the like; using the correct prt-get.conf prtdir settings, prt-get dup could be a good starting point (also for an automated script). This would minimize the work load caused by such updates (and IIRC this work load was the reason why we got rid of unmaintained in the first

Hi, On Thu, Oct 23, 2003 at 21:07:37 +0200, Markus Ackermann wrote: place). Maybe we could even provide anonymous CVS access, or use one of those wicked distributed version control systems :-) <dist-vcs> Imagine external contributors could just close our development tree, do some changes and host them somewhere; and maintainer could just pull the changes from their trees and merge them back; this would allow external contributors to work efficently independent of CLC, clc maintainer could get the patches very easily while keeping the perfect control which patches are added, and which are not. Some hot links: http://abridgegame.org/darcs http://www.venge.net/monotone (arch omitted intentally) </dist-vcs> Just an idea, though. Best regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Biel, Switzerland http://jw.tks6.net

Markus Ackermann wrote:

There are some updated unmaintained packages on http://www.maol.ch/crux/ [root@mob:~]# prt-get dup Hidden packages:

*snip*

I'll remove them from my repo as soon as there's an updated version in unmaintained.

Done, except for gtk-gnutella. Didn't compile for me, I think the new version is missing some files your port expects. Matt (jaeger@freenode/#crux)

There are some updated unmaintained packages on http://www.maol.ch/crux/

There are actually a LARGE number of old ports. I wrote a script to check for ports with updated files. Here's the results: http://plutor.org/projects/crux/prtaudit.html The script isn't extremely smart, so a few caveats: * What's listed is the minimum version number that it could find. If we're one version behind, we're likely more than one version behind. Check the package's web page before upgrading. * If a minor version number was updated, it might be a development tree, not stable. Again, check the web page. * If a major (or even minor) version changed, the files might end up being placed in a different location (like kernel source on kernel.org). So some ports with updated versions mighta been missed, plus sometimes package names change, so even MORE ports mighta been missed. * There's a small number of packages that don't have the version number verbatim in the source file name. For example, bin2iso. My script isn't smart enough to check these. That said, this script recognized 83 of the 321 unmaintained ports, which is 25.8%. Also, currently, the script is kinda ugly and slow, so you'll have to trust me on it. Once I get it cleaned up a little bit, I'll share it. Logan