[RFC] New name for 'repositories' - 'baskets'

[Jan Hudec]

On Wed, Mar 01, 2006 at 08:01:59 +1100, Robert Collins wrote:
> On Tue, 2006-02-28 at 15:07 +0100, Wouter van Heyst wrote:
> > On Tue, Feb 28, 2006 at 08:42:34AM -0500, James Blackwell wrote:
> > <snip>
> > 
> > > > I refer to 'shared repositories' to talk about repositories which are a
> > > > parent directory of many branches, and those branches have no repository
> > > > co-located at their directory.
> > > 
> > > Yes. We all agree with this. The problem is that we're using the term
> > > 'repository' which is incompatible with the CVS/SVN world. There's two
> > > ways to deal with this. 
> > > 
> > >  1. We not rename anything. CVS/SVN get confused because standalone
> > >     branches have repositories and the thing that they're used to thinking
> > >     is a repository is now called a 'shared repository'.
> > > 
> > >  2. We rename 'shared repositories' into 'repositories'. This means that
> > >     there is a need to come up with a name for what we currently call
> > >     repositories. I'm in favor of this option.
> > > 
> > >  3. We rename shared repositories into something else. This seems to be
> > >     the method that Jan is in favor of.
> > 
> > 4. Eliminate the difference.
> 
> So an important note here - in the internal code of bzr the 'sharedness'
> of a repository is taken into consideration in precisely two code paths:
>  * when cloning to preserve that status
>  * when determining if a repository can be used by a branch.
> 
> Other than that there is are conditionals looking at is_shared.
> 
> I don't understand how calling the same object doing the same job as
> both the large scale repository and the small repository storing history
> for a single branch different names can be a good idea.

I agree, that the object should have a name. But from users perspective,
the Repository(is_shared=true) is manipulated by user explicitly, while
the Repository(is_shared=false) is created behind the scenes and the
user does not need to think about it. However when explaining the
concept, you need a name for Repository() as well.

So one term for the thing created with 'make-repository' command. And
other term for the place where revision data is stored. I don't really
care whether they will be called 'baskets' and 'repositories', 'shared
repositories' and 'repositories', 'repositories' and 'storages' or
whatever, but it's important to stabilize the terminology.

> I think I need to -see- this confusion in action.

-- 
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060301/4cc2dac5/attachment.pgp