site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com User-agent: Thunderbird 1.5 (Macintosh/20051201) I was only joking, but it made for an attention-grabbing headline ;-) * Download of complete source archives for each project Cheers, Graham. -- Graham Lee UNIX Systems Manager, Oxford Physics Practical Course http://users.ox.ac.uk/~wadh1342 _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... On 28/3/06 19:55, Kevin Van Vechten wrote: Oh sure, defend Solaris but not my source browser... OK, so what I see is that it's "prettier" (i.e. enscript is run on the source files) and that there's source searching. These features are nice, no doubt. The source searching has been invaluable to me which is why I set this up; I was getting bored of searching google for "symbolName inurl:10.4.5.ppc site:darwinsource.opendarwin.org" However, I'm curious if anyone has any suggestions for integrating a few of our requirements that this doesn't seem to address: * Multiple releases hosted on the site: 10.0, ..., 10.3, ..., 10.4.5 That could be done by grabbing each release and storing it in SCM - opengrok can act like CVSweb in that regard if the SCM repository is local to the server. I only didn't do this because it wasn't immediately of use to me, but it certainly would be possible to come up with a script which: * rsyncs a given release from darwinsource.opendarwin.org * stages it into a temporary area * commits it to a CVS/SVN repository with a message like "changes for release 10.x.y" * updates the opengrok source tree from SCM then rebuilds the tags building this up would take a lot of time, it took the best part of today just to build the tags for 10.4.5.ppc. I'm not sure at the moment how to handle x86-vs-ppc or apple-vs-od branches, but I expect it could be done in the SCM. And as I originally said, the real benefits of using SCM (tracking changes/assigning blame ;-)) can't be used here because we don't have that information. But maybe tracking changes between releases is enough. TBF that's not handled by any of the existing source browsers either, but a separate rsync service. A bit of sqlite magic can accomplish the same thing too of course, using darwinbuild. I'd say that the ability to see which project provides a given file on the installed filesystem would be useful, too - darwinsource.opendarwin.org has this and darwingrok doesn't. This email sent to site_archiver@lists.apple.com