Pierre Neidhardt <m...@ambrevar.xyz> writes:
> Would that still be needed if we implement a tlpdb-based importer? The importer only helps you generate the initial package definition. A tlpdb-based importer cannot do magic. The tlpdb file tells it what files are expected to be provided by the package and what files are considered sources, but this doesn’t change the fact that these files come from different parts of the TeX Live SVN tree and somehow have to be added as inputs. The importer can automate this by adding the various native inputs, but you still end up with an ugly package definition. Think of all of the native inputs you’ll have to update when updating an existing package definition… Changing the way the input sources are represented is independent from the way this representation is generated. -- Ricardo
