ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Braslau via ntg-context <ntg-context@ntg.nl>
To: "amano.kenji" <amano.kenji@proton.me>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Bruce Horrocks <ntg@scorecrow.com>
Cc: Alan Braslau <braslau.list@comcast.net>
Subject: Re: How can I make a Gentoo Linux package for ConTeXt LMTX?
Date: Mon, 15 Aug 2022 12:46:10 -0600	[thread overview]
Message-ID: <78a4ac51-cc43-dc42-70a6-492d55c56000@comcast.net> (raw)
In-Reply-To: <WMoapxeIc1suuWMGwWE0JVqHfgnt0gC9FHP0fur9foASCHo1ihtr_FnCo1E3QI9xKgy43qMa9ZVE2HqMkTDZC1-4HKrv-z7nsiC-kndiJy0=@proton.me>

I believe that you are missing the point of LMTX.

LMTX Context is intended to be a self-contained AND PORTABLE directory 
tree. It does not need system installation paths and such and is 
designed to happily co-exist with system installed TeX (using packages) 
or TeXlive or others, without interference. The LMTX directory tree is 
very light-weight and indeed many production users might keep a separate 
copy with EACH major TeX project, thus ensuring that the project will 
continue to compile without changes as LMTX evolves. This strategy can 
be a successful insurance that very old projects will continue to 
compile yielding the same results many years later.

Not that you need to go that far.

Many users install LMTX for a system-wide use in some commonly 
accessible location. This is totally portable: only the PATH needs to be 
set to find the correct context executable.

LMTX does not go the route of system packages as this relies on package 
maintainers. ConTeXt mkiv with luatex continues to be made available and 
updated with TeXlive, so any system packages that provide TeXlive can 
provide ConTeXt.

Alan



On 15/08/2022 07:54, amano.kenji via ntg-context wrote:
>  From my perspective, a few optimizations for system installation need to happen for ConTeXt.
> 
> contextcnf.lua needs to support system installation paths.
> 
> Arch Linux texlive-core packages has its own patched version of texmfcnf.lua that sets TEXMFSYSVAR=/var/lib/texmf, TEXMFOS=/usr/share, TEXMFDIST=/usr/share/texmf-dist, and TEXMFSYSCONFIG=/etc/texmf.
> 
> TexLive's own version of texmfcnf.lua is not suitable for system-wide installation.
> 
> contexcnf.lua assumes all paths are relative to /path/to/extracted-archive which is definitely not a system-wide installation.
> 
> A system-wide installation is installed to absolute paths.
> 
> On top of that, there needs to be a document called INSTALLATION or BUILD that offers a simplified version of build/installation instructions contained in install.sh, mtx-install.lua, and mtxrun.lua. It seems mtxrun can be used to build and install ConTeXt without internet access as long as all dependencies are already present.
> 
> If ConTeXt is optimized for system-wide installation by modifying contextcnf.lua and adding INSTALL or BUILD, then all POSIX-like operating systems will be able to easily make packages for ConTeXt. Not just Gentoo Linux.
> 
> Can anyone help me with optimizing ConTeXt for system-wide installation?
> 
> ------- Original Message -------
> On Monday, August 15th, 2022 at 12:12 PM, Bruce Horrocks <ntg@scorecrow.com> wrote:
> 
> 
>>> On 15 Aug 2022, at 13:03, amano.kenji via ntg-context ntg-context@ntg.nl wrote:
>>>
>>> TexLive has texmfcnf.lua that doesn't really work with texlive-context installed by linux distributions.
>>>
>>> Arch Linux has its own patched version of texmfcnf.lua.
>>>
>>> It seems I'd be better off with a linux package for ConTeXt LMTX.
>>>
>>> How can I build and install ConTeXt LMTX on Gentoo Linux or any linux distribution?
>>>
>>> I wish it was as simple as ./configure, make, and make install.
>>
>>
>> Install instructions for LMTX on Linux are here:
>> https://wiki.contextgarden.net/Installation
>>
>>
>> It's pre-built so there are no make steps.
>>
>> Try it and ask again if you have problems. :-)
>>
>> —
>> Bruce Horrocks
>> Hampshire, UK
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


-- 
--
Alan
___________________________________________________________________________________
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-15 18:46 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
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 [this message]
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=78a4ac51-cc43-dc42-70a6-492d55c56000@comcast.net \
    --to=ntg-context@ntg.nl \
    --cc=amano.kenji@proton.me \
    --cc=braslau.list@comcast.net \
    --cc=ntg@scorecrow.com \
    /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).