#608 closed defect (fixed)
<remove> doesn't honor <base>
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | nALFS - Back End (XML Handlers) | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: | jwrober@… |
Description
It might be less error-prone if this is left like this (forcing a profile writer to use the _full_ path name).
In that case, docs must be updated/fixed to mention that feature.
Or, an option can be added so the user can choose the behavior of <remove> (might be too confusing).
Change History (10)
comment:1 by , 21 years ago
qa_contact: | alfs-discuss@linuxfromscratch.org → alfs-log@linuxfromscratch.org |
---|
comment:2 by , 21 years ago
Owner: | changed from | to
---|---|
Version: | CVS → 1.1.7 |
comment:3 by , 21 years ago
comment:4 by , 21 years ago
Owner: | changed from | to
---|---|
Priority: | lowest → normal |
If not adding an option, I think we should at least add it under some macro, like REMOVE_HONORS_BASE or something.
comment:5 by , 21 years ago
Version: | 1.1.7 → CVS |
---|
Consider adding it to <download> and <unpack> as well.
comment:6 by , 21 years ago
Owner: | changed from | to
---|
comment:7 by , 21 years ago
Cc: | added |
---|
comment:9 by , 21 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:10 by , 20 years ago
Version: | CVS → SVN |
---|
Note:
See TracTickets
for help on using tickets.
I think it would be fine to make <remove> honor the base attribute. It's no more dangerous than mkdir/copy/link doing it, which they already do.
If you agree, assign this bug to me and I'll deal with it this weekend when I factor out the common code from the handlers into the library.