monotone-devel
[Top][All Lists]
Advanced

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

Re: [Monotone-devel] ikiwiki monotone support


From: Zack Weinberg
Subject: Re: [Monotone-devel] ikiwiki monotone support
Date: Mon, 25 Feb 2008 11:02:33 -0500

On Mon, Feb 25, 2008 at 4:28 AM, Brian May <address@hidden> wrote:
>  I can't help but be really sceptical, simply because "mtn sync", "mtn
>  pull", and "mtn merge" don't touch the workspace, and I would be
>  really surprised if they look at the _MTN directory, except to get the
>  default database.
>
>  In fact, this would suggest to me I might be correct:
>
>  address@hidden:~/tree/config$ strace -eopen mtn sync
[...]

This trace is misleading, because monotone has a bad habit of
stat()ing things before it open()s them. -e trace=open,stat,lstat will
give a clearer picture:

...
stat("/home/zack/src/monotone/S-vanilla/_MTN", {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
stat("/home/zack/src/monotone/S-vanilla/_MTN", {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
stat("/home/zack/src/monotone/S-vanilla", {st_mode=S_IFDIR|0755,
st_size=20480, ...}) = 0
stat("/home/zack/.monotone/monotonerc", {st_mode=S_IFREG|0644,
st_size=878, ...}) = 0
open("/home/zack/.monotone/monotonerc", O_RDONLY) = 4
stat("_MTN/monotonerc", 0x7fff6d2db7f0) = -1 ENOENT (No such file or directory)
stat("_MTN/format", {st_mode=S_IFREG|0644, st_size=2, ...}) = 0
stat("_MTN/format", {st_mode=S_IFREG|0644, st_size=2, ...}) = 0
open("_MTN/format", O_RDONLY)           = 4
stat("_MTN/options", {st_mode=S_IFREG|0644, st_size=115, ...}) = 0
stat("_MTN/options", {st_mode=S_IFREG|0644, st_size=115, ...}) = 0
open("_MTN/options", O_RDONLY)          = 4
stat("/home/zack/src/monotone/.monotone.db", {st_mode=S_IFREG|0644,
st_size=177602560, ...}) = 0
open("/home/zack/src/monotone/.monotone.db", O_RDWR|O_CREAT, 0644) = 4
...

Having just been through all this code as part of the .encapsulation
project, I can assure you that _MTN/monotonerc will be read for any
command that's executing inside a workspace, whether or not the
command itself manipulates the workspace, and in fact even if the
command is defined with CMD_NO_WORKSPACE.

zw




reply via email to

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