You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently adding some regression tests to pdfjam using l3build. Indeed this works pretty well and needs only those two lines in l3build.lua:
checkengines= {"engine"} -- small wrapper script to use `pdfjam` with `l3build`pvtext=".args" -- *.args files contain command line arguments for `pdfjam`
as long as engine lies in my search PATH.
I would like this to work as well, if I put engine in testfiles/support and use checkengines = {"./engine"}. Alas at several places in l3build-check.lua, we compute a file name using "." .. engine which leads to the error
mv: cannot move './build/result/demo.pdf' to './build/result/demo../engine.pdf': No such file or directory
This should be avoidable by always using "." .. basename(engine) instead of "." .. engine.
The text was updated successfully, but these errors were encountered:
I am currently adding some regression tests to
pdfjam
usingl3build
. Indeed this works pretty well and needs only those two lines inl3build.lua
:as long as
engine
lies in my searchPATH
.I would like this to work as well, if I put
engine
intestfiles/support
and usecheckengines = {"./engine"}
. Alas at several places inl3build-check.lua
, we compute a file name using"." .. engine
which leads to the errorThis should be avoidable by always using
"." .. basename(engine)
instead of"." .. engine
.The text was updated successfully, but these errors were encountered: