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, 23 Aug 2022 10:25:02 +0000 [thread overview]
Message-ID: <Ni3pZMReV6UxDcmrqn2id1idFRuBSwAxzwFO_oON__pGJKZH5RR2PB5UczMeAeM4_LwFcoixYr2ZeRjSHaMN7ChNvAV0O9VYVwyUqFRWtgA=@proton.me> (raw)
In-Reply-To: <5cbf83e07f52f42662d209b23824e15cffa413d2.camel@telus.net>
> https://tug.org/TUGboat/tb34-3/tb108preining-distro.pdf
Somebody needed to update TeX Live on Gentoo Linux. I'm going to read it.
> From a developer perspective, this is essentially just the base ConTeXt files, a modified texmfcnf.lua, and a fairly basic makefile.
I'm going to read https://github.com/vlasakm/context soon. Until then, I would feel confused and disoriented.
------- Original Message -------
On Tuesday, August 23rd, 2022 at 1:11 AM, Max Chernoff <mseven@telus.net> wrote:
> Hi Amano,
>
> > Wuh. That's a bit complex.
>
>
> Not really. From a user perspective, all that you need to run is
>
> make install
>
> From a developer perspective, this is essentially just the base ConTeXt
> files, a modified texmfcnf.lua, and a fairly basic makefile.
>
> > For distribution packages that depend on context for generation of PDF
> > documents, having context as a system package is essential.
>
>
> I'd say that ConTeXt is available in nearly every package manager, via
> TeX Live. Very very few package managers would have no TeX Live. TeX
> Live only includes MkIV, the "stable" version, but most users won't
> notice many differences from MkXL/LMTX, the "experimental" version.
>
> By policy, TeX Live only updates its binaries once per year. This would
> be pretty much unworkable with LuaMetaTeX due to its frequent upgrades.
> At some point when LuaMetaTeX is stable, the source will be released and
> almost certainly be incorporated in TeX Live.
>
> > And, distribution maintainers can make things work if they understand
> > TeX directory structure and texmfcnf.lua.
>
>
> Packaging/installing ConTeXt is actually much easier than doing so for
> other TeX systems. With other systems, you need to fiddle around with
> fonts and packages, but with ConTeXt, you can pretty much just unpack a
> few files.
>
> Here's a short paper that should give you an overview of how hard
> packaging TeX can be:
>
> https://tug.org/TUGboat/tb34-3/tb108preining-distro.pdf
>
> > It comes down to care. If they care and they have installation guide,
> > they will make it work.
>
>
> I'm not sure who you're talking about here. If you're talking about end-
> users, then yes, it's pretty simple to install ConTeXt. I personally
> find ConTeXt much easier to install than TeX Live.
>
> If you're talking about packagers, then packaging ConTeXt is no more
> complex than packaging TeX Live (which of course includes ConTeXt MkIV).
> The installer documentation for ConTeXt LMTX certainly isn't as detailed
> as it is for TeX Live, but LMTX is still beta software.
>
> If you're trying to say that the ConTeXt developers don't care, then you
> may be "right" in a sense, but missing the point entirely. There is no
> one who is paid to work on ConTeXt: all of the developers work on it
> either as volunteers or to support their own business needs. The current
> installer works for them and for many other users. This isn't to say
> that they don't care about the users, but rather that they are unlikely
> to spend much time making a package for a fairly unpopular distro where
> the official installer already works.
>
> > On Sunday, August 21st, 2022 at 7:13 PM, Michal Vlasák <lahcim8 at gmail.com> wrote:
>
>
> Hi Michal,
>
> > > I prepared a proof of concept, that I am ready to take down immediately
> > > at Hans' request, since I don't handle license information properly, and
> > > texmf-context is stripped down (just so that the downloads are not too
> > > big for proof of concept).
> > >
> > > https://github.com/vlasakm/context
>
>
> That's quite impressive!
>
> > > There is documentation about how it can be used. I hope its obvious how
> > > I got "texmf" (texmf-context.zip, unzip, delete some files I didn't want
> > > to take up space),
>
>
> One suggestion: instead of unpacking and committing "texmf-context.zip",
> I'd recommend adding
>
> https://github.com/contextgarden/context-mirror/
>
> as a git submodule. That way, it's easy to keep the files up-to-date, your
> repo will use less space, and there's a clearer separation between your
> package files and ConTeXt itself.
>
> > > A bit of a disclaimer: I don't really recommend pursuing this further.
> > > Some time ago I was also that foolish to try to package TeX for Linux
> > > distributions. Unfortunately I think that the result will never by
> > > optimal - as demonstrated by the previous discussions, the usual
> > > purposes of packages (to integrate software into the system) don't apply
> > > much to TeX / ConTeXt - there one wants something more or less self
> > > contained (so that updates are under control, no random non-essential
> > > libraries brake things, etc.).
>
>
> Well packaging the files into .rpm/.deb isn't really a bad idea; what's
> bad is the weird modifications that distros make, plus the fact that
> nearly every distro delays updates by quite some time. I generally agree
> that installing TeX straight from the source is better, although I can
> see why some users prefer to install from their distro repos.
>
> Thanks,
> -- 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-23 10:25 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
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 [this message]
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='Ni3pZMReV6UxDcmrqn2id1idFRuBSwAxzwFO_oON__pGJKZH5RR2PB5UczMeAeM4_LwFcoixYr2ZeRjSHaMN7ChNvAV0O9VYVwyUqFRWtgA=@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).