Optimize build process #17
apriljunge
started this conversation in
Ideas
Replies: 1 comment 2 replies
-
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I just tried to set up a development environment and have a few suggestions on how to improve the process.
Let's discuss if they work and what you think about them. Maybe it would make sense to split the tasks if you agree that it should be done.
This build script could have a parameter like
--target
where you can specify if you want to build something specific (docs, snippets, ...) or all. If not specified the script could ask what to do.You don't have to cd for tests etc. Most build scripts could be unified into one (see 1.)
I am really unsure about this, because I do not know what's exaclty the magic behind copying the files to different folders. It didn't work for me. I could fix it by setting the environment vairable
TEXINPUTS
(example below for test.sh). Maybe this snippet could replace the copy process? Then maybe the script doesn't need super user rights any more? The environment variable modifies the directories where pdflatex looks for sty files (stackexchange discussion)The information scripts give about their parameter didn't help me very much: "Usage: dev-install.sh [-q] [-b]".
Maybe this could be enhanced a little.
Give short introduction in commands, what you need installed etc. Could be in CONTRIBUTING.md oder README.md
Beta Was this translation helpful? Give feedback.
All reactions