Bazaar filesystem handling confused by Cygwin

[Aaron Bentley]

When Bazaar is invoked under Cygwin, the reported platform is "cygwin", but windows filesystems still lack support for the execute bit.
sys.platform does not report "win32", so the special Windows x-bit handling is not activated.

The obvious answer is to treat the x-bit the same on "cygwin" as on "win32". Can cygwin run on other platforms?

[Aaron Bentley (abentley)]

Oh, and of course it would be better if we detected x-bit support by filesystem type, not by platform.

[John A Meinel (jameinel)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aaron Bentley wrote:
> Oh, and of course it would be better if we detected x-bit support by
> filesystem type, not by platform.
>

Actually Cygwin bzr *does* support setting the executable bit. I think the
problem is that if you do a checkout on cygwin, and then a status with win32
native, we would have a problem.

Also, it may be that it only works on NTFS, I'm not possitive what it
specifically takes to support executable. But I do know that if you use cygwin
it will track the mode for you, and bzr has worked that way for a long time.
(It could be broken, I haven't tested it recently).

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGaIftJdeBCYSNAAMRAqpIAKCrsgpXJxI0LXieR/Kpdb2IYxwZogCgtEB6
jZtaowlKJMhRlPOsCkCONos=
=dB7d
-----END PGP SIGNATURE-----

[John A Meinel (jameinel)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John A Meinel wrote:
> Aaron Bentley wrote:
>> Oh, and of course it would be better if we detected x-bit support by
>> filesystem type, not by platform.
>
>
> Actually Cygwin bzr *does* support setting the executable bit. I think the
> problem is that if you do a checkout on cygwin, and then a status with win32
> native, we would have a problem.

Oh, and it actually sounds like he did a checkout using win32 native, and then
did 'bzr status' in cygwin, since that would cause all of the X-bits to become set.

He could do "cygwin-bzr revert" which should fix everything.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGaJrDJdeBCYSNAAMRAq5CAKC3UjBP/ZAt8kFm/h9biZqMTz7BogCfeh4B
6LZjk1al4XRi45e/4axhxOc=
=kf6m
-----END PGP SIGNATURE-----

[Alexander Belchenko (bialix)]

> The obvious answer is to treat the x-bit the same on "cygwin" as on "win32".

IMO the answer is NO. Who want to use Cygwin should run cygwin version of bzr, not windows native version.

> Can cygwin run on other platforms?

From cygwin website:

"Cygwin is a Linux-like environment for Windows."

I'd prefer to mark this bug as invalid.

[Alexander Belchenko (bialix)]

Cygwin uses heuristics do determine x-bit on FAT32, and try to store x-bit-like information on NTFS. But this information is easily could be destroyed by native windows programs. So relying on Cygwin in this aspects is possible only when user uses working tree on cygwin exclusively via cygwin's programs, IMO. Either way has its pros and cons.

[Launchpad Janitor (janitor)]

[Expired for Bazaar because there has been no activity for 60 days.]