PR 6611 created for this issue on develop-9.0 https://github.com/livecode/livecode/pull/6611
The submitted change will preserve symbolic links. Relative links that go outside of the included directory will probably break. Absolute links may not work on other machines. All framework links should be self-contained and work fine. Ended up using "mv" on Mac/Linux to rename the files to preserve directory symbolic links. Something interesting that I discovered, if you use a symbolic link as the folder to include, it already would resolve that link and copy the actual linked directory into the app. At the top of __revSBCopyFolder, "revSBReadLink" turns the pSource into the actual path of the contents. I can't see a way to actually do this in the IDE though (if you choose a symbolic link, then the referenced folder is what is added). On Sat, Jul 21, 2018 at 11:25 PM, Brian Milby <br...@milby7.com> wrote: > Found something very interesting and I think it may be a bug (at least an > anomaly)... > > if you rename a symbolic link to a folder, the folder that is pointed to > is renamed vice the link > > consider the following (-> denotes a symbolic link) > ~/tmp/ > ~/tmp2 -> ./tmp/ > > rename "~/tmp2" "~/tmp3" > > results in > > ~/tmp2 -> (broken link, still points to ./tmp/ which does not exist) > ~/tmp3/ > > I checked on MacOS and Linux. > The call causing this problem is in "revRedirectMacOSResourcesRecurse" > > This particular issue won't impact ".bundle", ".app", nor ".framework" > folders since they are not relocated. > > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode