You don't have to install anything. What I'm asking is documentation of offline installation instructions. Offline installation means downloading all required archives in advance and then installing them without internet access.
Translation of what install.sh roughly does into a documentation that any OS package maintainer can read and adapt to one's operating system. What would you tell a system admin to do if instructions contained in install.sh have to be done manually by hand? For example, you can add a plain text file called INSTALL that has a list of commands that build or install ConTeXt into any directory structure. If you provide instructions for installing ConTeXt into an arbitrary directory structure and how to adjust contextcnf.lua to the new directory structure, package maintainers can adapt. ------- Original Message ------- On Thursday, August 18th, 2022 at 5:16 PM, Hans Hagen <j.ha...@freedom.nl> wrote: > On 8/18/2022 4:08 PM, amano.kenji wrote: > > > Sorry for spamming the list a little bit. > > > > If there was something like > > https://www.linuxfromscratch.org/lfs/view/stable/chapter06/ncurses.html for > > ConTeXt and luametatex (binary), then distribution maintainers can make > > packages for ConTeXt easily. > > > > I don't know TeX/TeXLive/kpathsea/ConTeXt directory structure conventions. > > Linux package maintainers don't know, either. I have packaged hundreds of > > programs, and TeX derivatives are monsters. > > > > Most users just install texlive OS package, use TexLive upstream installer, > > or use ConTeXt upstream install.sh. > > The problem with something context is that there are basically only two > components: > > - a tex tree with fonts and macros > - a few binaries (just one for lmtx) > > while in texlive one has quite some choices. We made these minimals > actually in order to not end up with complex system dependent > installations, also because most users just install context this way (it > is fast too). > > So, as Alan explained, anyone can wrap differently based on that. And if > something is needed, we can provide it. But I'm not going to install > something else than what i have for testing it. My develop and work > machine is windows pro + linux sub system, the servers run opensuse. On > all I just install under /data/context and that makes it system wide. I > don't need to set up something apart from adding a binary to the path > (or when I run from e.g. a web service I just use a fully quialified > path to mtxrun) .. it cannot be simpler than that. > > Hans > > ----------------------------------------------------------------- > Hans Hagen | PRAGMA ADE > Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > ----------------------------------------------------------------- ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___________________________________________________________________________________
