ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Archlinux: updated BPKGBUILD for luametatex
Date: Wed, 15 Dec 2021 23:43:44 +0100	[thread overview]
Message-ID: <6da56d03-bd2d-f9b3-bcb4-9f4e5da2bb74@xs4all.nl> (raw)
In-Reply-To: <nycvar.YAK.7.77.849.2112151523540.2624339@ervasbepr.pvz.zptvyy.pn>

On 12/15/2021 9:32 PM, Aditya Mahajan via ntg-context wrote:
> On Wed, 15 Dec 2021, Michal Vlasák via ntg-context wrote:
> 
>> On Wed Dec 15, 2021 at 7:28 PM CET, Hans Hagen via ntg-context wrote:
>>> On 12/15/2021 6:22 PM, Aditya Mahajan via ntg-context wrote:
>>>> Hi all,
>>>>
>>>> I am changing the way modules are installed in the ArchLinux aur package for luametatex.
>>>>
>>>> https://aur.archlinux.org/packages/luametatex/
>>>>
>>>> Earlier, I was just sym-linking to the modules installed by context-minimals-git package (which I also maintain). However, some packages there were out of date (in particular pgf/tikz). The new PKGBUILD installs the modules directly from CTAN.
>>>>
>>>> The following modules are installed by default:
>>>>       filter, vim, visualcounter, pgf, pgfplots, circtuitikz
>>>>
>>>> You can install other modules by adding them in the PKGBUILD.
>>>>
>>>> I am not sure if anyone else actually uses this PKGBUILD to maintain an up-to-date installation of LMTX. If someone does use it, and wishes to add more modules to the default list, I'll be happy to do that.
>>> Just curious ... we have this
>>>
>>>> mtxrun --script ctan --packages --pattern=tikz
>>>
>>> which just gives info (at the time i made that the ctan api was bugged
>>> as it mixed up xml and json keys, but i'm not sure if that was fixed of
>>> became bug=feature for practical reasons)
>>>
>>> i never came to a 'download option' because it was ot clear where to
>>> download from .. are there zips?
>>
>> Not sure if it's for every package, but should be just
>>
>>      "http://mirrors.ctan.org/" .. data.ctan.path .. ".zip"
>>
>> in scripts.ctan.details.
> 
> This corresponds the "Download" link on the CTAN page of each package, but unfortunately, is not always in TDS format. For example, for pgf (which is locate at /graphics/pgf/base), we have
> 
> https://mirrors.ctan.org/graphics/pgf/base.zip
> 
> which lists all tex related files in base/tex sub-directory. The CTAN page (https://www.ctan.org/pkg/pgf) also has a field "TDS Archive", which lists:
> 
> http://mirrors.ctan.org/install/graphics/pgf/base/pgf.tds.zip
> 
> which is TDS compliant. The same is the case for circuitikz and pgfplots. So, it safer to use
> 
>      "http://mirrors.ctan.org/" .. data.ctan.path .. "/" .. pkg_name .. "tds.zip"
> 
> But, for context packages, CTAN does nto have the tds zips (I guess because the default zip is already TDS compliant). For example:
> 
>      https://www.ctan.org/pkg/context-filter
> 
> has the "download" link at the bottom but not the "TDS Archive" link.
> 
> In the end, since I am only installing 4-5 packages, it is simpler to input the URLs but hand rather than write code to automate the logic.
sure, once you know what/where it's not that much work and I admit that 
I only downloaded tikz for testing the 'loading bug' and a few fonts 
during my tex life)

btw, when I fetched tikz a few days ago I could not fetch the zip from 
the browser because it complained about some security issue but the 
command line wget worked ok

another aspect of additional files is that I like to keep my system 
uncluttered so e.g when I install fonts we just need the open type files 
that I then install in texmf-fonts/fonts/data/<author>/* instead of 
bothering about forther structure (in fact it doesn't really matter much 
where files end up as long as there is some system behind it)

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 / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2021-12-15 22:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 17:22 Aditya Mahajan via ntg-context
2021-12-15 18:28 ` Hans Hagen via ntg-context
2021-12-15 18:56   ` kaddour kardio via ntg-context
2021-12-15 20:08   ` Michal Vlasák via ntg-context
2021-12-15 20:32     ` Aditya Mahajan via ntg-context
2021-12-15 20:40       ` Joseph Wright via ntg-context
2021-12-15 22:38       ` Michal Vlasák via ntg-context
2021-12-15 22:46         ` Hans Hagen via ntg-context
2021-12-15 22:43       ` Hans Hagen via ntg-context [this message]

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=6da56d03-bd2d-f9b3-bcb4-9f4e5da2bb74@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).