DO NOT REPLY [Bug 40059] Add method to explicitly define symlinks in tar task
https://issues.apache.org/bugzilla/show_bug.cgi?id=40059 --- Comment #3 from Steve Loughran ste...@apache.org 2010-01-04 03:39:58 UTC --- Mike, nobody works on Ant in any paid form, the general rule is that to fix a problem that you have, the best way is to patch your local copy of the source, then submit a patch including those changes and some tests/documentation, as that is what is needed to get your patch in the main branch, There is a workaround, which is you create the (hanging) symlink in the source filesystem pointing to the final destination, and then tar it using the native tar command, instead of the tar task. I've been using this when creating RPMs. It isn't x-platform though, only works on a unix system. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 40059] Add method to explicitly define symlinks in tar task
https://issues.apache.org/bugzilla/show_bug.cgi?id=40059 --- Comment #4 from Mike Lehmann meiklehm...@gmx.de 2010-01-04 04:32:06 UTC --- (In reply to comment #3) There is a workaround, which is you create the (hanging) symlink in the source filesystem pointing to the final destination, and then tar it using the native tar command, instead of the tar task. I've been using this when creating RPMs. It isn't x-platform though, only works on a unix system. This is no work-around for us, because we work on Windows. If I would have the experience of how the tar format looks like, I've already would have done the change myself and maybe suggested a patch. Unfortunately, I haven't that experience. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 40059] Add method to explicitly define symlinks in tar task
https://issues.apache.org/bugzilla/show_bug.cgi?id=40059 --- Comment #2 from mklhmnn meiklehm...@gmx.de 2010-01-03 04:58:51 UTC --- I also a similar functionality: I want to create a Mac-specific .tar.gz bundle which should contain the application's .app directory structure containing a PDF-documentation file, but the documentation should also be accessible parallel to the .app directory structure, so the average user is able to view the documentation after unpacking the .tar.gz file (note: the .app directory structure on OS X usually is treated as file by the Finder). When we can expect this issue to be fixed? Currently, I don't know of a work-around, except of duplicating the .pdf file in both locations. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 40059] Add method to explicitly define symlinks in tar task
https://issues.apache.org/bugzilla/show_bug.cgi?id=40059 Stefan Bodewig [EMAIL PROTECTED] changed: What|Removed |Added Target Milestone|1.8.0 |--- -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 40059] Add method to explicitly define symlinks in tar task
https://issues.apache.org/bugzilla/show_bug.cgi?id=40059 Stefan Bodewig [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #1 from Stefan Bodewig [EMAIL PROTECTED] 2008-09-04 06:32:59 PST --- *** Bug 43689 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 40059] Add method to explicitly define symlinks in tar task
https://issues.apache.org/bugzilla/show_bug.cgi?id=40059 Kev Jackson [EMAIL PROTECTED] changed: What|Removed |Added Target Milestone|--- |1.8.0 -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
