Hello Stuart.

Stuart Henderson wrote in
<slrnrdv71u.2f43....@naiad.spacehopper.org>:
 |On 2020-06-08, Steffen Nurpmeso <stef...@sdaoden.eu> wrote:
 |> Pity they did not wave through .19 before freeze, plenty of time
 |> there would have been.
 |
 |"Plenty of time" "But it's just one port!"

And a small and minor one, sure.

 |With dozens of people trying to push through updates to ports they
 |are interested in before tagging too, there is not plenty of time.
 |(you already asked to hold 14.9.18, and nothing in changelog,
 |at least to someone who doesn't use s-nail themselves, really
 |seemed important enough to make an exception).

To me the three weeks in between .18 and the official 6.7
announcement where a long time, it depends on the point of view.
It is clearly a minor port, but for it, anything after v14.9.16
are all pure bugfix releases.  Nothing in changelog, i wonder what
this means?  I do not see per-port changelogs?  .18 had

  . a mailcap directive combination (mostly binary formats),
  . .smime-* automated password fallback lookup,

of which the latter i deem important, at least for those who have
password protected certificates and keys.  (As i no longer have.)
We did not have had a test for this specific case, just as for the
former, which does not bite me in practice either because i have

  application/pdf;\
    infile=%s\;\
      trap "rm -f ${infile}" EXIT\;\
      trap "exit 75" INT QUIT TERM\;\
      mupdf "${infile}";\
    test = [ -n "${DISPLAY}" ];\
    nametemplate = %s.pdf; x-mailx-async; x-mailx-test-once
  application/pdf;\
    pdfinfo %s\; pdftotext -layout %s -;\
    test = command -v pdfinfo >/dev/null 2>&1; \
    copiousoutput; nametemplate=%s.pdf; x-mailx-test-once

in my ~/.mailcap and so we fall through to the last one, since if
PDFs look important i usually `write' them somewhere before mupdf
comes into play.

I soon asked for holding it then, because there was one more
problem to fix, it is really superficial (was never seen in real
life), but since i also made the software OpenSSL 3.0 ready
i wanted to make another release, and it made no sense to update
to .18 and then .19, with all the machinery there is involved.

Nothing wild, it is just that as the maintainer of this thing
i would like to see that the best aka newest version is available
to whoever wants to fiddle around with this thing.  That's all.

Ciao,

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Reply via email to