ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "amano.kenji via ntg-context" <ntg-context@ntg.nl>
To: Alan <braslau.list@comcast.net>
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: Thu, 18 Aug 2022 13:44:34 +0000	[thread overview]
Message-ID: <ZerbsjtCx7VZXg8x6YoAzsudA2FkNoM7uUa4JWw0HHRYYgNtDN7YDNzvgT8t83X1JAYKBOLcrUQvNpBvXOSWk8Xy88WA7khf7buGIgqpmyw=@proton.me> (raw)
In-Reply-To: <20220818071645.0deb846a@boo.my.domain>

I really don't understand how TexLive is installed. On Gentoo Linux, the code that handles TexLive installation is complex. I can't reuse code that I don't understand.

I came from LaTeX background. I got sick of handling incompatible modules in LaTeX and decided to try ConTeXt. I had used texlive OS package. I just started learning ConTeXt.

In the vast majority of cases, `make install` installs everything.

In case of ConTeXt, there is no `make install`. So, there needs to be a document that teaches me which directories I can just copy each source directory of ConTeXt to. Copying luametatex to /usr/bin is going to be easy.

I never had to understand TexLive/ConTeXt directory structure because I just used TexLive OS package. Now, I'm stuck reverse-engineering a black box.

Am I supposed to execute the following commands in https://github.com/contextgarden/context-mirror?

```
cp fonts /path/to/usr/share/texmf-dist
cp context /path/to/usr/share/texmf-dist
...
```

If you teach package maintainers where directories can be installed, then the maintainers can adapt the instructions to their own linux distributions.

Example installation commands can help a lot.

install.sh handles the magic behind complex lua functions I don't understand.

------- Original Message -------
On Thursday, August 18th, 2022 at 1:16 PM, Alan <braslau.list@comcast.net> wrote:


> On Wed, 17 Aug 2022 17:42:18 +0200
> Hans Hagen via ntg-context ntg-context@ntg.nl wrote:
> 
> > sorry, i just can't spent time on all the possible variant ways of
> > installation .. that is up to volunteers
> 
> 
> OS distribution packages are the responsibility of maintainers.
> "Upstream" developers can, and do, respond to requests for changes that
> might make packaging for a particular OS easier, but this is not
> directly the responsibility of developers.
> 
> Most OS packages require patches for particularities of that OS
> environment. LMTX Context, being minimal and fully portable, should be
> very easy to package as most paths, fonts, etc. are determined
> dynamically. The Context distribution follows the TeX directory tree
> structure, and this might not be the practice of some OS, which, for
> example, might locate different resources on different branches of the
> system directory structure. Some OS distributions are very particular
> about this.
> 
> I cannot understand the thrust of this thread.
> 
> It appears that the only issue for now concerns the distribution of the
> luametatex source tree. This is not yet the case as luametatex has been
> undergoing much experimentation. A classic opensource depository
> would disrupt this experimentation as more people get involved in
> wanting to make modifications. I believe the intention is to make a
> release once luametatex development settles into a normal state.
> 
> 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-18 13:44 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 [this message]
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
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='ZerbsjtCx7VZXg8x6YoAzsudA2FkNoM7uUa4JWw0HHRYYgNtDN7YDNzvgT8t83X1JAYKBOLcrUQvNpBvXOSWk8Xy88WA7khf7buGIgqpmyw=@proton.me' \
    --to=ntg-context@ntg.nl \
    --cc=amano.kenji@proton.me \
    --cc=braslau.list@comcast.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).