Currently, the core repository contains the argparse, g, cdiff and corto (and nested) packages, in addition to the corto tool.
To slim down the corto repository, the three non-core packages should be split off. The main reason they are still part of the core repository is because the code generator (tools/corto/src/cortotool_pp.c) relies on this functionality.
Therefore, as part of this, the cortotool shall be split up as well, and be made modular. The different commands of the cortotool shall be moved to their own packages (save for a few builtin commands). This also makes more sense- for example, the functionality implementing corto test belongs to the test framework, and doesn't make much sense if the test framework isn't installed. This will allow the corto tool extension to be maintained on the cortoproject/test repository.
The tool packages shall be stored under driver/tool.
Currently, the core repository contains the
argparse,g,cdiffandcorto(and nested) packages, in addition to the corto tool.To slim down the corto repository, the three non-core packages should be split off. The main reason they are still part of the core repository is because the code generator (
tools/corto/src/cortotool_pp.c) relies on this functionality.Therefore, as part of this, the cortotool shall be split up as well, and be made modular. The different commands of the cortotool shall be moved to their own packages (save for a few builtin commands). This also makes more sense- for example, the functionality implementing
corto testbelongs to the test framework, and doesn't make much sense if the test framework isn't installed. This will allow the corto tool extension to be maintained on thecortoproject/testrepository.The tool packages shall be stored under
driver/tool.