Collin Funk wrote:
> So the --avoid modules are emitted in the order they are passed to
> gnulib-tool, but the actual modules will be alphabetically sorted.
> Therefore, I think the correct code would be:
>
> if len(avoids) > 0:
> actioncmd += ''.join([f" \\\n# --avoid={x}" for x in avoids])
> if len(modules) > 0:
> actioncmd += ''.join([f" \\\n# {x}" for x in sorted(modules)])
OK. For the --avoid options, things are clear now.
Regarding the modules to include:
> Here is the diff with the two sorted instructions removed.
So, it looks like the original gnulib-tool does some sorting of the
module names that gnulib-tool.py does not do yet, in some earlier
processing steps. Since this can affect other parts of the output,
it would be good to have the sorting at the same processing stage.
None of the 'sort' invocations in gnulib-tool are covered by an
entry in the gnulib-tool.py.TODO file. Therefore the most promising
approach to finding the cause of the difference is to
- go through all 'sort' invocations in gnulib-tool,
- find the corresponding place in pygnulib/ and see whether
sorting happens there as well or has been forgotten.
Bruno
