ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "amano.kenji via ntg-context" <ntg-context@ntg.nl>
To: Hans Hagen <j.hagen@freedom.nl>
Cc: "amano.kenji" <amano.kenji@proton.me>,
	Hans Hagen via ntg-context <ntg-context@ntg.nl>
Subject: Re: How can I make a Gentoo Linux package for ConTeXt LMTX?
Date: Fri, 19 Aug 2022 12:51:01 +0000	[thread overview]
Message-ID: <XxF5Vmk4sPIO0kmTm_O7mQ0EeDnIuls2NNA7jlhV-9Gs-YISUh6aha6PpdviTebBGmGdSn7vVdtNOCyqUICV7ONIQiQ6Y3Zz_5SealLGHQA=@proton.me> (raw)
In-Reply-To: <7c528d7c-8ef1-7ace-6dd1-f759a50c5114@freedom.nl>

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.hagen@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
___________________________________________________________________________________

  reply	other threads:[~2022-08-19 12:51 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 12:03 amano.kenji via ntg-context
2022-08-15 12:12 ` Bruce Horrocks via ntg-context
2022-08-15 12:19   ` amano.kenji via ntg-context
2022-08-15 17:00     ` Bruce Horrocks via ntg-context
2022-08-16 11:43       ` amano.kenji via ntg-context
2022-08-16 16:02         ` Hans Hagen via ntg-context
2022-08-17 13:09           ` amano.kenji via ntg-context
2022-08-17 15:42             ` Hans Hagen via ntg-context
2022-08-18 12:32               ` amano.kenji via ntg-context
2022-08-18 12:56               ` amano.kenji via ntg-context
2022-08-18 13:16               ` Alan via ntg-context
2022-08-18 13:44                 ` amano.kenji via ntg-context
2022-08-18 13:53                 ` amano.kenji via ntg-context
2022-08-22 22:52                   ` Alan via ntg-context
2022-08-18 14:08                 ` amano.kenji via ntg-context
2022-08-18 17:16                   ` Hans Hagen via ntg-context
2022-08-19 12:51                     ` amano.kenji via ntg-context [this message]
2022-08-19 13:06                       ` Hans Hagen via ntg-context
2022-08-19 13:03                     ` amano.kenji via ntg-context
2022-08-19 13:11                       ` Hans Hagen via ntg-context
2022-08-19 13:18                         ` amano.kenji via ntg-context
2022-08-20  7:31                           ` Hans Hagen via ntg-context
2022-08-15 13:54   ` amano.kenji via ntg-context
2022-08-15 18:46     ` Alan Braslau via ntg-context
2022-08-16 11:35       ` amano.kenji via ntg-context
2022-08-21 19:13 ` Michal Vlasák via ntg-context
2022-08-22  9:41   ` amano.kenji via ntg-context
2022-08-23  1:11     ` Max Chernoff via ntg-context
2022-08-23 10:15       ` amano.kenji via ntg-context
2022-08-23 10:25       ` amano.kenji via ntg-context
2022-08-24 20:21       ` Michal Vlasák via ntg-context
2022-08-24 21:32         ` Hans Hagen via ntg-context
2022-08-25  0:00           ` Michal Vlasák via ntg-context
2022-08-23 19:13     ` Aditya Mahajan via ntg-context
2022-08-24 12:30       ` amano.kenji via ntg-context
2022-08-15 21:56 Max Chernoff via ntg-context
2022-08-16 11:28 ` amano.kenji via ntg-context
2022-08-18  0:51 Max Chernoff via ntg-context
2022-08-18  7:31 ` Hans Hagen via ntg-context
2022-08-18 12:00 ` Henning Hraban Ramm via ntg-context

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='XxF5Vmk4sPIO0kmTm_O7mQ0EeDnIuls2NNA7jlhV-9Gs-YISUh6aha6PpdviTebBGmGdSn7vVdtNOCyqUICV7ONIQiQ6Y3Zz_5SealLGHQA=@proton.me' \
    --to=ntg-context@ntg.nl \
    --cc=amano.kenji@proton.me \
    --cc=j.hagen@freedom.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).