Run script before build

[daviddavo]

I'm forking a package that uses a .txt file.

Currently, I have to run a lua program that generates that file, and then run my build.lua file. Is there any hook I can use to run my txt builder program just before starting to build. I think docinit_hook and checkinit_hook are both too late, because I use docstrip and I need it before compiling the .ins

[josephwright]

We don't currently have a hook early enough. Could you illustrate the project structure in general terms or with a link?

[daviddavo]

I'm modifying the lipsum package

https://github.com/PhelypeOleinik/lipsum

As you can see, there are multiple lipsum-*.txt files, which will be converted to lipsum-*.ltd.tex inside \genlipsum (https://github.com/PhelypeOleinik/lipsum/blob/31c3d57d52ee69ab0ff0233f5a6869ca96542c37/lipsum.ins#L52)

My idea is to run a script that generates those lipsum-*.txt files.

[FrankMittelbach]

David

I'm modifying the lipsum package

what exactly do you mean by "modifying" the lipsum package? As it is under LPPL you should not alter it in situ and if you alter the file names why not do this off line rather than each time by script?

[daviddavo]

They are generated randomly, but I guess it's better to distribute the already generated files, and it will be easier to test.

About modifying it, sorry, I wanted to say "forking it", as is I will change the package name (and filenames) and distribute the source code.

[FrankMittelbach]

all good then :-) ... I didn't look what your project does ... it is just that getting different files with the same name in the TeX world is really bad since you never know what then happens, so when I saw "modifying" it just jumped at me