| 1 |
On Tue, 2009-07-14 at 17:07 +0200, Michael Haubenwallner wrote: |
| 2 |
> |
| 3 |
> Usually the files are just copied instead of symlinked there. |
| 4 |
> |
| 5 |
> But as far as I know, there is no Unix-ish OS without symlink support - |
| 6 |
> even Interix does support them. |
| 7 |
> Although I cannot definitively say we won't have to select between |
| 8 |
> multiple executables and/or shared libraries for native Windows once - |
| 9 |
> they would have to be copied instead of symlinked then. |
| 10 |
> |
| 11 |
> So it should be fine as long as 'symlink' can potentially be implemented |
| 12 |
> as 'copy' for specific platforms. |
| 13 |
> |
| 14 |
|
| 15 |
Can be done... |
| 16 |
|
| 17 |
def create_symlink(self, source, destination): |
| 18 |
self.delete_file(destination) |
| 19 |
os.symlink(source, destination) |
| 20 |
|
| 21 |
Therefore can be easily replaced for copy. What should be the default? |
| 22 |
Should uselect be able to supply both options like "uselect --copy bla |
| 23 |
bla" overrides os.symlink to copy function? |
| 24 |
|
| 25 |
> Thanks! |
| 26 |
> /haubi/ |
| 27 |
|
| 28 |
Thanks for the hint! |
| 29 |
|
| 30 |
Cheers, |
| 31 |
Sérgio |
| 32 |
-- |
| 33 |
Sérgio Almeida - mephx.x@×××××.com |
| 34 |
mephx @ freenode |
Archives