Discussion:
Packaging biblatex-ext: blxextdoiapi.lua in wrong directory
Add Reply
Moritz Wemheuer
2018-11-26 08:47:10 UTC
Reply
Permalink
Hi everybody,

it seems that the new file blxextdoiapi.lua of biblatex-ext got
installed into ./texmf-dist/doc/latex/biblatex-ext/. That file provides
a runtime Lua module that is called from a .sty file and so it should
live in a directory where it can be found, I assume
./texmf-dist/tex/latex/biblatex-ext/ would be a better fit.

Please move blxextdoiapi.lua from the doc directory into where it can be
found as a runtime file.

Is there anything I as the package developer could do to avoid these
kind of confusions over the correct place for a file in the future
(short of uploading a TDS zip to CTAN)?

Moritz
Martin Sievers
2018-11-26 14:01:45 UTC
Reply
Permalink
Post by Moritz Wemheuer
./texmf-dist/tex/latex/biblatex-ext/ would be a better fit.
I guess, it would rather be ./texmf-dist/tex/luatex/biblatex-ext/

Best regards
Martin
Moritz Wemheuer
2018-11-26 14:19:14 UTC
Reply
Permalink
Post by Martin Sievers
Post by Moritz Wemheuer
./texmf-dist/tex/latex/biblatex-ext/ would be a better fit.
I guess, it would rather be ./texmf-dist/tex/luatex/biblatex-ext/
I'll defer to your judgement and that of the other experts on that one.
As long as the file is found I'm OK with anything that makes sense, but
I notice that for fontspec we have
./texmf-dist/tex/latex/fontspec/fontspec.lua and for microtype
./texmf-dist/tex/latex/microtype/microtype.lua
Karl Berry
2018-11-26 21:44:19 UTC
Reply
Permalink
Please move blxextdoiapi.lua from the doc directory into where it can be
found as a runtime file.

Thanks, done for tonight.

Is there anything I as the package developer could do to avoid these
kind of confusions over the correct place for a file in the future

1) Add a note in the README. But even more likely in this case, with an
already-extant package:

2) When adding a new runtime .lua (or other "nonstandard"-extension)
file to the package, include a note about it when you upload to CTAN.
The CTAN people are good about passing on such notes to Christan and me.

Thanks for all,
Karl

P.S. By "nonstandard" I mean that .sty, .cls, .?bx, code.tex, .ldf,
etc., etc., are all included in the runtime by default, so there is no
need to worry about them. (ref: $standardtex in tlpkg/libexe/ctan2tds.)

I can't install .lua by default because .lua files are often supposed to
end up in different places, e.g., for scripts, or just for doc building, etc.
Moritz Wemheuer
2018-11-26 22:02:51 UTC
Reply
Permalink
Post by Moritz Wemheuer
Please move blxextdoiapi.lua from the doc directory into where it can be
found as a runtime file.
Thanks, done for tonight.
Thank you very much.
Post by Moritz Wemheuer
2) When adding a new runtime .lua (or other "nonstandard"-extension)
file to the package, include a note about it when you upload to CTAN.
The CTAN people are good about passing on such notes to Christan and me.
Very good, I'll try to keep that in mind.

Moritz

Loading...