monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] setup creates _MTN/mtn.db


From: hendrik
Subject: Re: [Monotone-devel] setup creates _MTN/mtn.db
Date: Sat, 8 May 2010 19:28:10 -0400
User-agent: Mutt/1.5.18 (2008-05-17)

On Sat, May 08, 2010 at 02:08:35PM +0200, Thomas Keller wrote:
> Am 08.05.10 13:44, schrieb Stephen Leake:
> > A recent change lets setup init a new database _MTN/mtn.db if none is given.
> > 
> > First, this needs to be documented in the manual; both that setup will
> > init the database if it is not already, and that it provides a default
> > name.
> 
> Yes, I forgot that and I'll do it shortly. Thanks for he reminder.
> 
> > Second, what is the rationale, both for providing any default name, and
> > choosing this particular name?
> 
> The rationale is simply to make monotone less database-centric and
> verbose with respect to the commands needed to start with a fresh project.
> 
> > I can see that proving a default db name it makes it easy to start a
> > totally new project. But it's a significant change, and I'm not happy
> > with the path.
> > 
> > I'm ok with initializing the database if needed.
> > 
> > Once the project grows a branch that they want to checkout into a
> > different directory, having the database in <branch_1>/_MTN/mtn.db will
> > be very odd and confusing; people will wonder if there should be one db
> > per branch, or one db per workspace.
> > 
> > I think ~/.monotone/mtn.db would be a better place for the default
> > database.
> 
> Those people who store their databases elsewhere have to specify their
> complete path now anyways and setup now basically follows the same
> principles like clone (even uses the same path). Beside that, setup even
> informs the user that it creates a new database in _MTN/, which clone
> currently does not iirc.
> 
> So let me repeat again, what I wanted to improve is the situation for
> first time users and I personally find a place like ~/.monotone/mtn.db
> not a good place at all (what if the user starts another, different
> project - should we reuse the same database then?), because its much
> hidden and maybe even physically away from the actual workspace setup.

Last thing I want is to create a random data base when I just forget to 
mention what database I want to use.

-- hendrik




reply via email to

[Prev in Thread] Current Thread [Next in Thread]