From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2775 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Steve Litt Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: s6 usability Date: Sun, 22 Dec 2019 15:33:27 -0500 Message-ID: <20191222153327.6ee088bd@mydesk.domain.cxm> References: <20191125214342.y7lx5mixrljr6s27@gromit.local> <20191127203307.ohaameqfgncm52h5@gromit.local> <20191129140901.klifpegc74iv4zul@klumpi.ignorelist.com> <20191221092639.p5iid3y3csmni4iw@klumpi.ignorelist.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="121293"; mail-complaints-to="usenet@blaine.gmane.org" To: supervision@list.skarnet.org Original-X-From: supervision-return-2364-gcsg-supervision=m.gmane.org@list.skarnet.org Sun Dec 22 21:33:34 2019 Return-path: Envelope-to: gcsg-supervision@m.gmane.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1ij7uu-000VRD-SS for gcsg-supervision@m.gmane.org; Sun, 22 Dec 2019 21:33:33 +0100 Original-Received: (qmail 6517 invoked by uid 89); 22 Dec 2019 20:33:56 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Original-Received: (qmail 6510 invoked from network); 22 Dec 2019 20:33:56 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; h=X-Originating-IP:Date:From:To:Subject:Message-ID:In-Reply-To:References:X-Mailer:MIME-Version:Content-Type:Content-Transfer-Encoding; s=default; d=troubleshooters.com; b=jf1TzaCOXAu6+aOF3j3nVx0SxBP554hXVCkfy283/ATmLhUSxBTqkUQcK4B+ZSQ8i5TCwUvU4Dns9WvagZxOUzikG2G35Bo3RqJigxLTRsg5c78Os/eapv8WWLio936HNZWkQkUCWjVTCQ4XsIOrhhrQPdfSmCM6ZYHGr4rFLxk=; DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; d=troubleshooters.com; s=default; t=1577046808; bh=bDI8NFr8rh/wedx1H9ddqekJS28=; l=2462; h=X-Originating-IP:Date:From:To:Subject:Message-ID:In-Reply-To: References:X-Mailer:MIME-Version:Content-Type: Content-Transfer-Encoding; b=I0PDUGLDIwvdW4QTn3OCvtniuGU49G179P9nk+L60Ik8fbJHE0/+8OO/Ykmul1X/N ZvkPu5Gy4YbxFov3KoBF/2L1oUCVRhcEvDNoUQ6OPLdDZbBt/f7nueXMhIwtt37A8J CG872VV8cFezzsh1+YVn5SHyrEGcYwlvkXBg0hCU= X-Originating-IP: [72.188.224.222] In-Reply-To: X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-unknown-linux-gnu) Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2775 Archived-At: On Sat, 21 Dec 2019 23:46:34 +0000 "Laurent Bercot" wrote: > No, you're falling for the pretext - because this is only the current > pretext they're using. Debian *does not provide* a POSIX-compliant cd > binary, so their claims at POSIX compliance are just lies. > The current version of execline includes POSIX-compliant cd and wait > binaries, and the next one will also include a POSIX-compliant umask > binary. Then we shall see what new excuse they find not to put > execline binaries in the default PATH. My finding in the past is that Debian will do harm to any software just so they can comply with their arcane rules. One such rule caused them to change the prepend key-sequence in VimOutliner from the incredibly quick and easy double comma (,,) to the wrist-twisting, error prone, slow, and keyboard dependent double backslash (\\), even though VimOutliner's manifesto listed authoring speed as the top priority. That being said, is having your stuff on the executable path such an advantage? A lot of times I put all the executables for a system in a directory off the path, and then create a shellscript like this: ==================================== #!/bin/sh export PATH=/path/to/s6:$PATH $@ ==================================== Or this: ==================================== #!/bin/execlineb -s1 importas OLDPATH PATH export PATH "/path/to/s6:$OLDPATH" $1 $@ ==================================== Symlink the shellscript from a directory on the path, and whatever is in $@ is as good as being on the path. By doing this I avoid any program name conflicts, I can easily delete my whole program or copy it to another computer. And of course slashpackage is another way. I'm not saying this is perfect. I'm just saying it could be as simple a opening a tarball in an arbitrary directory and typing make; make install. That's basically how we distributed VimOutliner for a long time. Earlier in this thread somebody suggested a method of Debian packaging that was both breathtaking in its convolution and preventing of other software from being installed at the same time. With Debian's propensity to break things doing them their way, perhaps it's time to consider the possibility of doing an end run around the Debian Developers. SteveT Steve Litt December 2019 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21