#11836 closed defect (fixed)
fs-traverse should take a list of directories
Reported by: | kballard (Lily Ballard) | Owned by: | kballard (Lily Ballard) |
---|---|---|---|
Priority: | High | Milestone: | MacPorts 1.4 |
Component: | base | Version: | 1.4.3 |
Keywords: | Cc: | ||
Port: |
Description
Currently fs-traverse takes a dynamic number of arguments, each of which is a directory to search. Instead it should take a single argument which is a list of directories.
Change History (7)
comment:1 Changed 18 years ago by kballard (Lily Ballard)
comment:2 Changed 18 years ago by kballard (Lily Ballard)
Aaaaand I meant to do a preview on that comment to make sure my links worked, which obviously they didn't. Oops.
comment:3 Changed 18 years ago by sfiera@…
As of r24403, kernel-tools no longer depends on this behavior.
comment:4 Changed 18 years ago by kballard (Lily Ballard)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in r24410
comment:5 Changed 18 years ago by jmpalacios (Juan Manuel Palacios)
Milestone: | MacPorts 1.5 → MacPorts 1.4 |
---|---|
Version: | → 1.4.3 |
comment:6 Changed 17 years ago by nox@…
Priority: | Important → High |
---|
comment:7 Changed 17 years ago by jmpalacios (Juan Manuel Palacios)
Merged into the release_1_4 branch in r24908.
-jmpp
Note: See
TracTickets for help on using
tickets.
Currently openssl and kernel-tools use fs-traverse. openssl just uses it to traverse one directory, so no change is needed. kernel-tools traverses 3 directories, so the Portfile would need changing, which unfortunately breaks compatibility with 1.4.3. The alternative solution is to make fs-traverse do both at the same time - a dynamic number of arguments, each which can be a list. Then when 1.4.4 (or 1.5) is released, we can change the Portfiles. The problem with this is it's unnecessarily complicated from a usage perspective. I don't really want to support a function which behaves like that. We could leave it as undocumented behaviour, and then remove it post-1.5, but that's still ugly.
Another solution might be to fix this to take the list, update kernel-tools, and shove out a 1.4.4 immediately, but that just adds to the whole "release diarrhea" issue.