[Scons-dev] New symlink copy support

[Kenny, Jason L]

I agree. In Parts we added code to allow Symlinks to work as a first class object ( ie a node) In Scons. It seems to work just fine. As long as some simple rules are followed it we have not had issues on windows and or linux/mac at this point.

Jason

From: Scons-dev [mailto:scons-dev-bounces at scons.org] On Behalf Of Gary Oberbrunner
Sent: Saturday, July 26, 2014 10:33 AM
To: SCons Dev List
Subject: Re: [Scons-dev] New symlink copy support


What's wrong with copying symlinks if that's what the user wants?

I have some pure python Windows symlink code lying around somewhere too. Works fine on NFL.

--
Gary Oberbrunner
(sent from my Android)
On Jul 26, 2014 10:14 AM, "anatoly techtonik" <techtonik at gmail.com<mailto:techtonik at gmail.com>> wrote:
Is it true that Copy now tries to copy symlinks by
default?

Symlinks is a can of worms. I'd avoid using them
unless explicitly enables at all costs.

1. os.symlink is documented as unix only
https://docs.python.org/2/library/os.html#os.symlink
2. even if os.symlink is present, it may fail
(especially in shared folders mounted in VM)
https://mail.python.org/pipermail/python-ideas/2014-July/028386.html

--
anatoly t.
_______________________________________________
Scons-dev mailing list
Scons-dev at scons.org<mailto:Scons-dev at scons.org>
http://two.pairlist.net/mailman/listinfo/scons-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://two.pairlist.net/pipermail/scons-dev/attachments/20140728/cce7dc11/attachment.html>