[rfc] Windows symlink support

[James Blackwell]

On Sat, Jan 14, 2006 at 11:21:20AM -0700, Stuart Jansen wrote:
> 1) Users are allowed to commit symlinks by default. Any time a symlink
> is modified and commited, near the end of the commit output the user is
> informed that symlinks are not portable and may cause problems on other
> platforms. The user is further informed that this warning can be
> disabled by changing a setting in the user's global configuration. 

I think this is an ideal situation for a plugin. A portability plugin
would be easy to install and could either warn or prevent issues that
are not portable to windows.

You wouldn't even need all of the developers running it, though it would
help detection. One person with the plugin could say "Whoah, we're doing
things that don't work well on windows".

> Concerns: My understanding is that bzr is trying to avoid an explosion
> of configuration options. I also wonder how this will affect scripting
> of bzr as well as alternative interfaces other than the command line.

When its reasonable to do so.

-- 
James Blackwell's home :  http://jblack.linuxguru.net
Gnupg 06357400   F-print AAE4 8C76 58DA 5902 761D  247A 8A55 DA73 0635 7400
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060114/191c23df/attachment.pgp