Re: texlive-fetch instead of svn-fetch

Hey Ricardo! Ricardo Wurmus skribis: > Tex Live packages often have a complicated source file layout. They > don’t usually come in a nice self-contained tarball. Instead they are a > mosaic of files that are sourced from different parts of the Tex Live > SVN tree. For many Tex Live packages t

Re: texlive-fetch instead of svn-fetch

Thanks for clarifying this. Then I 100% agree with your approach. I should have a little bit more free time in the coming days, so I'll (finally) get down to write the tlpdb importer :) -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

Re: texlive-fetch instead of svn-fetch

Pierre Neidhardt 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 fi

Re: texlive-fetch instead of svn-fetch

Hi, Would that still be needed if we implement a tlpdb-based importer? -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

texlive-fetch instead of svn-fetch

Hey Guix, Tex Live packages often have a complicated source file layout. They don’t usually come in a nice self-contained tarball. Instead they are a mosaic of files that are sourced from different parts of the Tex Live SVN tree. For many Tex Live packages the “source” field is insufficient, so