Oops, never replied to this. On Fri, Oct 26, 2007 at 08:15:05PM -0500, Ken Williams wrote: > > On Oct 26, 2007, at 1:05 PM, Nicholas Clark wrote: > > > > >Are you running rsync without --delete? > >[Do you have files such as ext/B/C/C.xs? They're long dead. If so, > >re-run > >rsync with --delete. I'd suggest testing with --dry-run first - -- > >delete is > >dangerous and has caused people to need to resort to backups before] > > Thanks, got blead built now and I see the xs.t failure. > > I always hope (against hope, I guess) that I can do an rsync (without > --delete) & build without a full rebuild, but I guess that's a > pipedream. > > Is there read-only p4 access for blead available maybe? That would > be super-cool.
Not in the general, anonymous case, no. Partly this is because of how ActiveState have the repository security and authentication setup (via an ssh tunnel), per person. But as I understand it in the more general case open anonymous perforce access via the perforce mechanism is opening a denial of service attack, as perforce stores all state on the server, so it can't scale infinitely if "infinite" interested people worldwide each check the code out. (Yes, checking code out creates server-side state) Specifically there would be no problem if you followed the instructions in Porting/repository.pod and asked for read access. Nicholas Clark
