| 1 | | Currently [browse:trunk/dports/devel/openssl/Portfile openssl] and [browse:trunk/dports/sysutils/kernel-tools/Portfile 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. |
| | 1 | Currently [browser:trunk/dports/devel/openssl/Portfile openssl] and [browser:trunk/dports/sysutils/kernel-tools/Portfile 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. |
