ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Max Chernoff via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Max Chernoff <tex@maxchernoff.ca>
Subject: [NTG-context] Re: upload
Date: Sat, 14 Jun 2025 04:24:32 -0600	[thread overview]
Message-ID: <890bc1a4db5e1ffaef5cb73ada015cc9fa4fb895.camel@maxchernoff.ca> (raw)
In-Reply-To: <4e630d7f-13f3-4790-9f97-1f2cbd6d2b13@xs4all.nl>

Hi Hans,

On Sat, 2025-06-14 at 11:45 +0200, Hans Hagen wrote:
> > in this past week. Even the perpetually-stable pdfTeX had a few bugs
> > earlier this year.
>
> oh ... i thought that pdftex was very stable and admit that i never
> check mkii with that (i just assume that when we can make a mkii format
> we're fine)

I remember the one bug being a spacing issue that only showed up with
very specific documents, the other bug I accidentally introduced while
fixing a different bug (oops). Both bugs were fixed before TL25 was
released (or maybe it was shortly after?), so MkII should be fine.

> > Karl updates the packages in TL every day; most days there are 3--8
> > different packages that get updated. And it's pretty common for packages
> > to be updated multiple times in a week (often after a new major version
> > was released), and there are a few packages that are consistently
> > updated almost every week.
>
> hm, times have changed ... (i wonder how that impacts users who expect
> for instance fonts and patterns to be the same over time but maybe they
> juist don't update or at least not hit the update button without checking)

Most of the font authors are pretty careful to not change the metrics in
updates, so that's not usually a big deal. But hyphenation patterns
definitely change, so most users who care about identical page breaks
will just use a frozen (and usually ancient) version of TeX Live and
never upgrade.

> > > like monthly update or so that we can then adapt to?
> >
> > Sure, I can reduce the update frequency if you want; right now it's set
> > to check for updates daily, but it's easy to change it to every second
> > day/weekly/monthly/etc. My thinking was that since all software has
> > bugs, frequent updates in TL will shorten the interval between people
> > reporting bugs and them receiving the fix. Or I can let the autoupdater
> > run daily most of the time, but then disable it during the weeks of
> > BachoTeX and the ConTeXt Meeting (when updates tend to be more
> > frequent).
>
> let's for now keep an eye on matters and evaluate later

Ok, sounds good to me. Let me know if/when you want me to change
anything.

> > > but that is a bit hard to catch realiable
> >
> > If the file "context-papersize.tex" exists (full path:
> >
> >      $TEXMFCONFIG/tex/context/user/context-papersize.tex
> >
> > ), then the user has ran "sudo tlmgr paper [letter|a4]"; otherwise, TeX
> > Live will use the default settings. So the only case that you should
> > need to check for is if "context-papersize.tex" contains the following
> > contents:
> >
> >      \setuppapersize[letter][letter]
>
> if maybe just if that file is there, right?

If you run "tlmgr paper a4" the file will contain

    \setuppapersize[A4][A4]

which is probably not worth warning over.

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://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2025-06-14 10:30 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d91a8a34-3870-43c1-abfd-5098a7e99a71@xs4all.nl>
2025-06-14  6:47 ` Max Chernoff via ntg-context
2025-06-14  7:41   ` Hans Hagen
2025-06-14  8:47     ` Max Chernoff via ntg-context
2025-06-14  9:45       ` Hans Hagen
2025-06-14 10:24         ` Max Chernoff via ntg-context [this message]
2025-02-12 11:05 [NTG-context] upload Hans Hagen
2025-02-12 14:48 ` [NTG-context] upload Steffen Wolfrum
2025-02-12 15:13   ` Hans Hagen via ntg-context
2025-02-13 14:28     ` Steffen Wolfrum
2025-02-13 16:37       ` Hans Hagen
2025-02-14 10:36         ` Steffen Wolfrum
2025-02-14 10:57           ` Steffen Wolfrum
2025-02-14 15:50             ` Pablo Rodriguez via ntg-context
2025-02-14 16:13               ` Hans Hagen
2025-02-14 17:05                 ` Pablo Rodriguez via ntg-context
2025-02-14 18:18                   ` Hans Hagen
2025-02-15 13:10                     ` Pablo Rodriguez via ntg-context
2025-02-14 10:58           ` Hans Hagen
2025-02-14 11:29             ` Steffen Wolfrum
2025-02-14 12:26               ` Hans Hagen
2025-02-14 19:03                 ` Steffen Wolfrum
2025-02-14 19:43                   ` Hans Hagen
2025-02-15 19:07                     ` Steffen Wolfrum
2025-04-29 11:12                     ` Steffen Wolfrum
2025-04-29 14:38                       ` Pablo Rodriguez via ntg-context
2025-02-15 13:16                   ` Pablo Rodriguez via ntg-context
2025-02-15 18:29                     ` Steffen Wolfrum
2025-02-16  9:03                       ` Pablo Rodriguez via ntg-context
2025-02-16 10:09                         ` Thomas Meyer
2025-02-16 10:36                           ` Pablo Rodriguez via ntg-context
2025-02-16 10:57                             ` Thomas Meyer
2025-02-16 11:02                               ` Pablo Rodriguez via ntg-context
2025-02-16 11:09                                 ` Thomas Meyer
2025-02-18 12:02                         ` Steffen Wolfrum
2025-02-18 16:19                           ` Pablo Rodriguez via ntg-context
2025-02-19  6:22                             ` Steffen Wolfrum
2025-02-21 11:32                               ` Steffen Wolfrum
2025-02-25 16:01                                 ` Pablo Rodriguez via ntg-context
2025-02-28 11:44                                   ` Steffen Wolfrum
  -- strict thread matches above, loose matches on Subject: below --
2024-09-17 11:52 [NTG-context] upload Hans Hagen
2024-09-17 20:12 ` [NTG-context] upload Henning Hraban Ramm
2024-09-18 18:12   ` Pablo Rodriguez via ntg-context
2024-09-18 18:28     ` Henning Hraban Ramm
2024-07-31 17:55 [NTG-context] upload Hans Hagen via ntg-context
2024-07-31 18:57 ` [NTG-context] upload Henning Hraban Ramm
2024-08-01  7:21 ` Henning Hraban Ramm
2024-08-01  7:44   ` Hans Hagen
2024-04-01  7:31 [NTG-context] upload Hans Hagen
2024-04-01  8:17 ` [NTG-context] upload Mikael Sundqvist
2024-04-01  9:34 ` Otared Kavian
2024-04-01  9:48   ` Hans Hagen
2024-02-14 12:44 [NTG-context] upload Hans Hagen
2024-02-15  9:02 ` [NTG-context] upload luigi scarso
2024-02-15  9:35   ` Mikael Sundqvist
2024-02-15  9:48   ` Hans Hagen
2024-01-17 23:13 [NTG-context] upload Hans Hagen
2024-01-18  1:35 ` [NTG-context] upload Otared Kavian
2024-01-18  6:29   ` Mikael Sundqvist
2024-01-18  7:17     ` Jeong Dal via ntg-context
2024-01-18 14:27       ` Otared Kavian
2024-01-18 14:49         ` Hans Hagen
2024-01-18 19:04 ` Alain Delmotte
2024-01-18 19:43   ` Denis Maier via ntg-context
2024-01-19 17:34     ` Pablo Rodriguez via ntg-context
2024-01-19 18:55       ` Denis Maier via ntg-context
2024-01-19 21:56       ` Otared Kavian
2024-01-20  7:41         ` Alain Delmotte
2024-01-20  8:38       ` Hans Hagen via ntg-context
2024-01-20  8:58         ` vm via ntg-context
2024-01-20  9:32           ` Ursula Hermann
2024-01-20  9:45             ` Hans Hagen
2024-01-23  9:09             ` Hans Hagen via ntg-context
2024-01-23 16:29               ` Otared Kavian
2024-01-23 18:02                 ` Bruce Horrocks
2024-01-23 20:08                 ` Hans van der Meer via ntg-context
2024-01-23 20:59                   ` Otared Kavian
2024-01-23 21:06                     ` Thomas A. Schmitz
2024-01-24  9:29                       ` Otared Kavian
2024-01-23 21:02                   ` Otared Kavian
2024-01-20 13:04         ` Pablo Rodriguez via ntg-context
2024-01-21 11:33         ` Alain Delmotte
2023-08-09 15:42 [NTG-context] upload Hans Hagen
2023-08-09 19:29 ` [NTG-context] upload Rik Kabel
2023-08-09 21:11   ` Hans Hagen
2023-08-10 12:57     ` Henning Hraban Ramm
2023-08-10 13:03       ` Hans Hagen
2023-08-10 13:33         ` Henning Hraban Ramm
2023-08-10 13:52           ` Wolfgang Schuster
2023-08-10 14:41             ` Hans Hagen via ntg-context
2023-08-10 15:02               ` Wolfgang Schuster
2023-08-10 16:14                 ` Henning Hraban Ramm
2023-08-11  1:31 ` Thangalin
2023-08-11  6:19   ` Hans Hagen
2023-08-11 16:41     ` Thangalin

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=890bc1a4db5e1ffaef5cb73ada015cc9fa4fb895.camel@maxchernoff.ca \
    --to=ntg-context@ntg.nl \
    --cc=tex@maxchernoff.ca \
    /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).