Phil Hannent [EMAIL PROTECTED] writes:
Stephen Leake wrote:
I don't believe there is a monotone that comes with MinGW.
Indeed, I meant the cygwin which was clearly apparent to you from my
version. Sorry for the confusion.
type -a mtn
$ type -a mtn
mtn is /usr/bin/mtn
mtn is /bin/mtn
mtn is /cygdrive/k/Program Files/monotone/mtn
mtn is /cygdrive/d/Program Files/monotone/mtn
mtn is /cygdrive/k/Program Files/monotone/mtn
mtn is /usr/bin/mtn
This is definitely going to cause confusion, if not other problems.
I suggest you maintain a simpler PATH variable, and change it for
particular applications.
As Timothy pointed out, the MinGW and Cygwin mtn's look for monotonerc
and the keys directory in different places
Indeed, however my use case is that I have a project which I am
working on for my employer and I use the Windows version for (which
works great) and the cygwin version which I use for working on Pidgin
builds.
THis is an excellent case for using different PATH settings for the
two different projects.
While I was aware of the two different locations I can confirm that
they contain the same information as I started my work project using
the cygwin version (with the keys from there) and changed to the MinGW
version.
The monotonerc file in both locations just contains the get_passphrase
function. The keys folder contains 2 keys.
When you have 2 keys, mtn doesn't know which one to use, so it is
almost as bad as having no keys. You need to specify which one to use,
using --key. I believe that is cached in the workspace _MTN/options.
Although that should be the same between Cygwin and MinGW versions.
--
-- Stephe
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
