Opened 16 years ago
Last modified 9 years ago
#195 new enhancement
Add relative directory support to archiver
| Reported by: | Steven Levine | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Release_3.25 |
| Component: | AddOns | Version: | |
| Keywords: | Cc: |
Description
The archiver needs an option to allow creating zip with relative paths. Currently all paths are relative to the root.
One way to implement this is with a Mimimize paths checkbox. FM/2 would select a working directory that minimizes the store path.
Another way is to allow the working directory to be specfied and minimize the paths based on the selection. This supports cases where the user wants a top level empty directory to be included in the zip. This directory name is typically the application name and version.
Change History (7)
comment:1 Changed 15 years ago by
| Milestone: | → Release_3.15 |
|---|
comment:2 Changed 15 years ago by
| Component: | fm/2 base → AddOns |
|---|
comment:3 Changed 13 years ago by
| Milestone: | → Release_3.20 |
|---|
comment:4 Changed 10 years ago by
| Milestone: | Release_3.22 → Release_3.23 |
|---|
comment:5 Changed 10 years ago by
comment:6 Changed 9 years ago by
| Milestone: | Release_3.23 → Release_3.24 |
|---|
Ticket retargeted after milestone closed
comment:7 Changed 9 years ago by
| Milestone: | Release_3.24 → Release_3.25 |
|---|
Note: See
TracTickets for help on using
tickets.
IMO there's no need to add another option. Just change the code to start an archiver from the parent dir of a specified file object.
On OS/2 we don't have fixed paths as on Linux, where that option makes sense. On OS/2 the proposed destination directory is usually changeable.
Other archiver GUIs I know behave so.
Andreas Schnellbacher