Re: [Monotone-devel] Re: Scalability question

[Jonathan S. Shapiro]

On Fri, 2006-08-04 at 21:38 +0200, Koen Kooi wrote:
> - On 8/4/06, Koen Kooi <address@hidden> wrote:
> >>
> >> Try:
> >> address@hidden:~/OE/monotone/org.openembedded.dev/packages/e17$ mkdir baz
> >> address@hidden:~/OE/monotone/org.openembedded.dev/packages/e17$ cd baz/
> >> address@hidden:~/OE/monotone/org.openembedded.dev/packages/e17/baz$
> >> touch foo
> >> address@hidden:~/OE/monotone/org.openembedded.dev/packages/e17/baz$ mtn
> >> add baz
> >> mtn: misuse: no such file or directory: 'packages/e17/baz/baz'

> I don't get why it matters in what directory I am to make monotone
> recursively add files.

Ah. Now I see the problem.

mtn path names in the workspace are relative to the current working
directory. When you execute the "mtn add" command, your current
directory is e17/baz, and indeed, there is no file or directory named
"baz" within the subdirectory e17/baz.

The mtn designers had two feasible choices here:

  1. Workspace paths are always relative to the project root, or
  2. Workspace paths are always relative to the current directory

Mtn implements the second choice. This is also what CVS and OpenCM do.

We polled potential users early on in the OpenCM project, and the
overwhelming consensus was that most users prefer the second choice.

Given the design choice about workspace path names, the command that you
wanted was one of:

        mtn add .
        mtn add ../baz

shap