supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Guillermo <gdiazhartusch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "supervision-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org"
	<supervision-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org>,
	 "skaware-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org"
	<skaware-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org>
Subject: Re: [announce] execline-2.5.0.0
Date: Mon, 2 Apr 2018 13:56:59 -0300	[thread overview]
Message-ID: <CADQ2Nw_1OOfrEvoXL3ugh6Lc_0DoFmzmH3zwPa7sg2AXHXbzMQ@mail.gmail.com> (raw)
In-Reply-To: <embfd02dc4-6eb8-4ef8-9b9b-580e151f24d0@elzian>

2018-04-02 7:39 GMT-03:00 Laurent Bercot:
>
>  User reports have come in by the hundreds and they are almost
> unanimous (sorry, Colin): they don't like the 2.4.0.0 change,
> pretending it hurts readability (as if), and writability too,
> of execline scripts. (What? People were actually writing execline
> scripts? Why haven't I heard of them before yesterday?)
>  They want a revert to the old syntax.
>
>  Users. They never know what they want.

My reaction:

1) "Oh, an announcement!" (timezone magic made this happen on Saturday for me)
2) "Wait, what? Whaaat?!"
3) All of this chaotically over a short period of time:
  * "How is something like this execline-2.4.0.0 and not execline-3.0.0.0?"
  * "Wait, is s6-linux-init still going to work? Did I miss a new
s6-linux-init release announcement?" (I don't know why my brains
focused on s6-linux-init instead of the major breakage of s6 and s6-rc
that not retaining the old names somehow would have produced)
  * "Wait, did he rename the C source files too? Like
src/execline/=.c, src/execline/;.c, etc.?"
  * "Wait, execline commands exist as executable files in the
filesystem, are the files going to actually have those names? Like
'test' and '['? That new makefile is going to be quite interesting..."
  * "Wait, are programs still going to be callable by their old names?"
    - "How? Compatilibity symlinks? Didn't he dislike multiple
personality binaries? Is execlineb going to implement the conversion
as part of its parsing?" (the latter could actually work?)
    - "Does every execline script need to be rewritten now? How many
of those are out there already?"
  * "Hmmm, using execline commands from a shell is going to be hell
now with all that character escaping."
  * "Well, on the other hand, maybe no more ImageMagick-like name collisions..."
  * "Let's see how many programs kept their names. Huh? ímport is still here?"
4) "I definitely have to take a closer look now."
5) "Oh."

G.


      parent reply	other threads:[~2018-04-02 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02 10:39 Laurent Bercot
2018-04-02 12:06 ` John O'Meara
     [not found]   ` <CAPCpfp9rp-N5nK5=darnBFH0BzZ0yKrrKiXdWZWtOcxGzDPE+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-04-02 12:07     ` John O'Meara
2018-04-02 12:12       ` John O'Meara
2018-04-02 12:13   ` Alex Efros
2018-04-02 16:56 ` Guillermo [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=CADQ2Nw_1OOfrEvoXL3ugh6Lc_0DoFmzmH3zwPa7sg2AXHXbzMQ@mail.gmail.com \
    --to=gdiazhartusch-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=skaware-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org \
    --cc=supervision-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org \
    /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).