Re: kernel.bkbits.net off the air

[Andrew Walrond <andrew@walrond.org>]

On Friday 14 Nov 2003 3:00 pm, Larry McVoy wrote:
> On Thu, Nov 13, 2003 at 08:57:53PM +0000, Andrew Walrond wrote:
> > The point. You got one major o/s project hosted on bk when you ought to
> > have them all. Loads more developers using bk at home means loads more
> > demanding it at work.
> >
> > And all it would take is a lobotomised, redistributable, license free
> > client so anyone can pull o/s software from bk repos.
>
> One of us is not getting it, maybe it's me.  To build something like
> you describe is pretty easy IF AND ONLY IF all you are asking for is an
> update mechanism.  As soon as you want revision history, diffs, rollbacks,
> modifiable files, etc., you have to go to real BK.  Is that OK?  All you
> want is a "keep me up to date" mechanism?  No diffs, no history, it's a
> replacement for tarballs and patches?

Yes exactly. Fundamentally I want *anybody*, without restriction, to ge able 
to pull and update sources from any open-source project hosted with bk.

The requirements are the equivalent functionality to:

lobobk clone ...
lobobk -r co
lobobk pull
lobobk export -r tag dest

Ie, Get a local clone of the repo, Be able to keep it updated, checkout the 
head version and export any particular tagged version.

and absolutely nothing else.

Not necessary, but if the cloned repo  was complete enough to be recloned, It 
would also make the perfect tool for anyone wanting to host a coherent mirror 
of the repo. Which takes us full circle I believe :)

Andrew Walrond