Skip to content

More updates to archlinux setup instructions#845

Merged
brucemiller merged 4 commits into
brucemiller:masterfrom
tkw1536:archlinux-setup-updates
Jul 13, 2017
Merged

More updates to archlinux setup instructions#845
brucemiller merged 4 commits into
brucemiller:masterfrom
tkw1536:archlinux-setup-updates

Conversation

@tkw1536

@tkw1536 tkw1536 commented Jun 23, 2017

Copy link
Copy Markdown
Contributor

This PR makes more updates to the archlinux setup instructions -- in particular incorporating the suggestion from @dginev in the last commit to install via CPAN instead.

@dginev

dginev commented Jun 23, 2017

Copy link
Copy Markdown
Collaborator

For the record, my suggestion was to install via cpanm, which should also be platform-independent.

Can be as simple as:

cpanm git://github.com/brucemiller/LaTeXML.git

or if you are working from the clone itself:

cpanm .

Adding a --notest in there makes it quite fast for doing quick builds while developing and still using the simple latexmlc (and friends) commands without specifying any concrete paths. This is definitely the easiest way to work if you don't have sudo access to a machine, everything can live in the user's home directory.

Readme is quite good too:
https://github.com/miyagawa/cpanminus/

@tkw1536

tkw1536 commented Jun 23, 2017 via email

Copy link
Copy Markdown
Contributor Author

@brucemiller

brucemiller commented Jun 23, 2017 via email

Copy link
Copy Markdown
Owner

@brucemiller

brucemiller commented Jun 23, 2017 via email

Copy link
Copy Markdown
Owner

@dginev

dginev commented Jun 23, 2017

Copy link
Copy Markdown
Collaborator

Sounds great! Btw knowing Tom, he may want to also create an example LaTeXML docker image and upload it to https://hub.docker.com/ , given that he's had plentiful Docker experience at KWARC.

In fact funnily enough there seems to already be one:
https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=0&q=latexml&starCount=0

The usual question is what a docker image is actually useful for - and the main answer is quickly spinning up microservices of a certain kind. A common example nowadays, with cloud latex startups popping up left and right, is starting an array of worker machines with texlive capability, which becomes very easy once you have:
https://hub.docker.com/r/harshjv/texlive-2015/

Whether there is any usefulness of preparing this also for the main latexml versions, and whether Tom should be the one doing that is another question, so this is just a random thought and not a real short-term suggestion. We're yet to dockerize our LaTeXML setup at Authorea, as we're yet to farm out that work, but once we do we would probably use docker hub for that.

@tkw1536

tkw1536 commented Jun 23, 2017

Copy link
Copy Markdown
Contributor Author

@dginev Looking at the docker image you linked that seems to be using the version that is in the debian repository - which may not be the best idea.
If I do make one (we should probably have a separate issue on that), I would very much prefer basing it on a different method so that we do not have to rely on the distributions to upgrade their repositories.

@tkw1536

tkw1536 commented Jun 25, 2017

Copy link
Copy Markdown
Contributor Author

I have written and added a paragraph on how to install via cpanm.

tkw1536 and others added 4 commits July 1, 2017 13:46
When running test cases on archlinux, it turned out that a specific
package was missing from the listed dependencies. This commit adds the
relevant package.
After a note from @dginev, this commit adds a recommendation to install
from sources via CPAN to the setup instructions for archlinux.
@tkw1536 tkw1536 force-pushed the archlinux-setup-updates branch from 42c3d49 to 2710244 Compare July 1, 2017 17:46
@brucemiller brucemiller merged commit c6c6116 into brucemiller:master Jul 13, 2017
@tkw1536 tkw1536 deleted the archlinux-setup-updates branch July 13, 2017 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants