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: Thomas Keller
Subject: Re: [Monotone-devel] setup creates _MTN/mtn.db
Date: Sat, 08 May 2010 14:08:35 +0200
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; de; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b2pre Thunderbird/3.0.4

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.

Thomas.

-- 
GPG-Key 0x160D1092 | address@hidden | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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