bazaar-ng 0.7 released

[John Arbash Meinel]

Jari Aalto wrote:
> Martin Pool <mbp at sourcefrog.net> writes:
> 
>>    * The parent of Bzr configuration directory can be set by BZR_HOME
>>      environment variable. Now the path for it is searched in BZR_HOME, then
>>      in HOME. Under Windows the order is: BZR_HOME, APPDATA (usually
>>      points to C:\Documents and Settings\User Name\Application Data), HOME.
>>      (John Arbash Meinel)
> 
> 
> Please differentiate 
> 
>        - Windows
>        - Cygwin
> 
> I assume that under Cygwin it searches as expected: BZR_HOME, HOME, APPDATA.
> and not in order: BZR_HOME, APPDATA, HOME.

I don't know that it should search APPDATA for cygwin. It doesn't right
now. The current check is
	BZR_HOME
	if sys.platform == 'win32':
		APPDATA
		HOME
	else:
		os.path.expanduser('~')

> 
> Hm. I'm wondering why it has to be BZR_HOME, APPDATA, HOME in any
> case? For example I have permanent setting of Windows environment
> variable
> 
>     HOME
> 
> in Windows registry and I would be very upset if bazaar used APPDATA before
> looking if HOME is set. You see, the Win32 Native Emacs also needs
> the HOME variabale in order to find "~".
> 
> Jari

Well, IIRC the "correct" place for windows applications to put their
information is in APPDATA.

I'm not sure that HOME should trump that. In fact, I know that *I* don't
want it to. Because when I'm in a cygwin shell, I have $HOME set to
cygwin home, but I might be running the Windows native version of bzr.
Which means that paths would be incorrect. Since C:/cygwin/home/jameinel
has stuff like /cygdrive/c/dev/bzr/bzr.dev, while $APPDATA would have
stuff like C:/dev/bzr/bzr.dev

I'm willing to make changes if the general belief is that HOME trumps
APPDATA. I wrote it, and I have a use case that says APPDATA should
trump. I can always play with aliases to get BZR_HOME to point to the
right place when I invoke bzr. (The native windows version is ~50%
faster than the cygwin version for filesystem operations, so I want to
use it as much as possible).

So if you can convince me that my setup is atypical, we'll change it.

I know I've seen domains which mount a network share to something like
'H:' and then set $HOME to point to that share. I don't remember exactly
what this changes, other than running 'cmd.exe' starts in $HOME, rather
than C:/Windows/System or somesuch.

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060123/f8868359/attachment.pgp