Hello everyone, I've been implementing changes in httpup to allow syncronisation of subtrees of a repository and found out that it might be an option for us to get packages from external packagers into the CLC CVS tree. I've written a short explanation in the Wiki, find it at http://crux.fh-regensburg.de/cgi-bin/cvstrac/wiki?p=HttpupNg With such a solution, we could easily keep up with external packagers, given they provide their ports in an httpup repository. Imagine they could just submit a bug report "there's a new version of fluxbox, sync it from http://my.domain/ports/clc-upstream#fluxbox". Sidenote: We might solve the problems with 'unmaintained' with something like this. <interlude> A comment for people aware of httpup repositories: Packagers could use the following layout for their private repository: clc-upstream/ portA private/ portB portC The "supfile" for ports(8) would check out the private subtree; once a port is accepted into CLC (as externally maintained port), the maintainer moves it into clc-upstream from where the CLC maintainer syncs it to the CLC CVS tree. The maintainer can even decide to put a new version of a port into 'private' first (so people subscribing to his private collection will get the new version immediately) and move it to clc-upstream only if it has been synced. </interlude> The new version which is going to be released as httpup 0.3.0 has gone through a major refactoring, so I'd appreciate testing of the current release (2.90) very much; to do so, just update the 'version' variable in contrib/httpup (new md5: eb78e8dec74d9e9417dc19033a0ab1fe) and pkgmk -d -u (or prt-get edit httpup Pkgfile && prt-get update httpup). There might be a few minor changes before the release of 0.3.0 and a 'diff' command if I can find a good way to do it; probably not for .0 though. Comments, suggestions, ideas? Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net