From: "amano.kenji via ntg-context" <ntg-context@ntg.nl>
To: Max Chernoff <mseven@telus.net>
Cc: "amano.kenji" <amano.kenji@proton.me>, ntg-context@ntg.nl
Subject: Re: How can I make a Gentoo Linux package for ConTeXt LMTX?
Date: Tue, 16 Aug 2022 11:28:06 +0000 [thread overview]
Message-ID: <boFT2Roq_kU5mSVTd1svPmgfLiLdz716C7q6KMljHZlB2z6inuSVOcQnI880_ZIP80E_0v1ZnfeeY2o6HnxdxfV6N7um7HqmHaRTbD6xgos=@proton.me> (raw)
In-Reply-To: <feeaf39fa489262433012f486254df8288c11c26.camel@telus.net>
http://lmtx.pragma-ade.nl/install-lmtx/texmf-context.zip is not versioned.
If the file changes later, linux distributions refuse to use the file.
I wish ConTeXt and LuaMetaTex were versioned and provided `offline` build instructions. The vast majority of programs are versioned and can be built easily offline. Even if they were distributed as binary files, if they are versioned, I can still make linux packages out of them.
------- Original Message -------
On Monday, August 15th, 2022 at 9:56 PM, Max Chernoff <mseven@telus.net> wrote:
> Okay, I'm seeing a few separate issues here.
>
> 1. Gentoo expects to compile everything from source.
>
> This isn't an option here since LuaMetaTeX doesn't have any source
> available (yet). So for the time being, you'll need to use the provided
> binaries. These support pretty much every architecture, so this
> shouldn't really be a problem.
>
> 2. You want to install ConTeXt LMTX system-wide.
>
> This is doable with the standard Linux installer script. Just make sure
> to run the script as root and install the files in /opt/context. This is
> what I've done on my system, and it works quite well.
>
> $ ls -l $(type -p context)
> lrwxrwxrwx. 1 root root 10 Jul 28 00:33 /opt/context/tex/texmf-linux-64/bin/context -> luametatex*
>
>
> 3. You want to install ConTeXt without any network access.
>
> The easiest way to do this would be to install on a system with
> internet, then just copy over the files.
>
> If you want to use the "original" installer files, it shouldn't be
> impossible, but probably not too easy either. (All steps below are
> untested)
>
> The platform-independent stuff is all in one big zip, located at:
>
> http://lmtx.pragma-ade.nl/install-lmtx/texmf-context.zip
>
> Unzip this file as "<context root>/tex/texmf-context/".
>
>
> Then you also need to download all of the binaries. You will need to
> download all of the paths listed in this file:
>
> http://lmtx.pragma-ade.nl/install-lmtx/tex/texmf-linux-64.tma
>
> All of those files need to be placed in "<context root>/tex/texmf-linux-
>
> 64/bin".
>
> Then to finish installing you'll need to run "mtxrun --generate" and
> "context --make". There are probably a bunch of other steps that I'm
> missing, but this should get you close.
>
> Again, probably easier to just use the regular installer.
>
> 4. ConTeXt is really picky about texmfcnf stuff.
>
> This is an issue that I've had too:
>
> https://github.com/latex3/l3build/issues/232
>
> Pretty much any modification of anything texmfcnf-related with ConTeXt
> will completely prevent it from running. There's a thread discussing the
> problem (but with no real solutions) here:
>
> https://tug.org/pipermail/tex-live/2020-September/046099.html
>
> And a Wiki page here:
>
> https://wiki.contextgarden.net/Custom_Configuration
>
> I agree that this texmfcnf stuff makes it really difficult to install or
> use ConTeXt with any kind of custom paths. Does anyone know how to
> properly configure a texmfcnf with custom paths?
>
> Hopefully this is of some help.
> -- Max
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-08-16 11:28 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 21:56 Max Chernoff via ntg-context
2022-08-16 11:28 ` amano.kenji via ntg-context [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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
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='boFT2Roq_kU5mSVTd1svPmgfLiLdz716C7q6KMljHZlB2z6inuSVOcQnI880_ZIP80E_0v1ZnfeeY2o6HnxdxfV6N7um7HqmHaRTbD6xgos=@proton.me' \
--to=ntg-context@ntg.nl \
--cc=amano.kenji@proton.me \
--cc=mseven@telus.net \
/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).