[Scons-dev] New symlink copy support

[Kenny, Jason L]

Ideally that is the hope I have.. CCopy should be used as the backbone of all copied in Parts and I hope in SCons. Everything in Parts is done so it could be added to SCons. The license is MIT under Intel, but it is assumed that SCons will own all this code as it moves stuff over. Intel has no interest in controlling a build system.

Jason

From: Scons-dev [mailto:scons-dev-bounces at scons.org] On Behalf Of William Blevins
Sent: Monday, July 28, 2014 7:54 PM
To: SCons developer list
Subject: Re: [Scons-dev] New symlink copy support

Wow.  This is a pretty cool extension.

Now that I know what Jason is talking about with CCopy, I think it might have been a better idea to use CCopy as the backbone for the default Copy methodology (if licensing allowed), or is that overkill?

V/R,
William

On Mon, Jul 28, 2014 at 8:37 PM, Bill Deegan <bill at baddogconsulting.com<mailto:bill at baddogconsulting.com>> wrote:
William,

Jason and his team have created.
"Parts is an extension to SCons. It augments SCons by adding new concepts to aid with the development, organization and maintenance of large projects. Parts provides a standardized way to create plug-and-play components within or between products, saving time and development costs. "
parts.tigris.org<http://parts.tigris.org>
-Bill


On Mon, Jul 28, 2014 at 4:50 PM, William Blevins <wblevins001 at gmail.com<mailto:wblevins001 at gmail.com>> wrote:
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.

I'm trying to keep up here, but I'm missing some context.  What is Parts?

V/R,
William

On Mon, Jul 28, 2014 at 11:17 AM, Kenny, Jason L <jason.l.kenny at intel.com<mailto:jason.l.kenny at intel.com>> wrote:
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<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

_______________________________________________
Scons-dev mailing list
Scons-dev at scons.org<mailto:Scons-dev at scons.org>
http://two.pairlist.net/mailman/listinfo/scons-dev


_______________________________________________
Scons-dev mailing list
Scons-dev at scons.org<mailto:Scons-dev at scons.org>
http://two.pairlist.net/mailman/listinfo/scons-dev


_______________________________________________
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/20140729/1fff9a93/attachment-0001.html>