Re: Bug#906250: ITP: execline -- small and non-interactive scripting language

2018-09-03 Thread Jonathan Dowland
On Sun, Sep 02, 2018 at 02:42:36PM +0800, Shengjing Zhu wrote: * If I install them in path like /usr/lib/execline/bin, then I need to ensure this path are in everyone's PATH. Yes. This is similar to ccache; users will need to make sure they set their path correctly to use the package. -- ⢀⣴⠾

Re: Bug#906250: ITP: execline -- small and non-interactive scripting language

2018-09-03 Thread Ian Campbell
On Mon, 2018-09-03 at 10:17 +0200, Jakub Wilk wrote: > http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xcu_chap01.html#tag_23_01_07 TIL: there is a (slightly, but not insanely so) roundabout rationale for having a non-builtin `cd`... thanks! Ian.

Re: Bug#906250: ITP: execline -- small and non-interactive scripting language

2018-09-03 Thread Adam Borowski
On Mon, Sep 03, 2018 at 10:17:09AM +0200, Jakub Wilk wrote: > * Shengjing Zhu , 2018-09-02, 14:42: > > When I try to package execline(a non-interactive shell script)[1], it > > installs following binaries in default PATH, > > > > cd, if, exec, wait, > > Three of them (cd, umask, wait) clash

Re: Bug#906250: ITP: execline -- small and non-interactive scripting language

2018-09-03 Thread Shengjing Zhu
On Mon, Sep 3, 2018 at 4:43 PM Shengjing Zhu wrote: > > Three of them (cd, umask, wait) clash with shell's regular built-in > > utilities. POSIX requires them to be exec(2)able[0][1]. Debian doesn't > > currently provide standalone executables for them (which is a bug), but > > some other distros

Re: Bug#906250: ITP: execline -- small and non-interactive scripting language

2018-09-03 Thread Shengjing Zhu
On Mon, Sep 3, 2018 at 4:17 PM Jakub Wilk wrote: > > * Shengjing Zhu , 2018-09-02, 14:42: > >When I try to package execline(a non-interactive shell script)[1], it > >installs following binaries in default PATH, > > > >cd, if, exec, wait, > > Three of them (cd, umask, wait) clash with shell's

Re: Bug#906250: ITP: execline -- small and non-interactive scripting language

2018-09-03 Thread Jakub Wilk
* Shengjing Zhu , 2018-09-02, 14:42: When I try to package execline(a non-interactive shell script)[1], it installs following binaries in default PATH, cd, if, exec, wait, Three of them (cd, umask, wait) clash with shell's regular built-in utilities. POSIX requires them to be exec(2)abl

Re: Bug#906250: ITP: execline -- small and non-interactive scripting language

2018-09-02 Thread Ben Hutchings
On Sun, 2018-09-02 at 14:42 +0800, Shengjing Zhu wrote: > Dear -devel, > > When I try to package execline(a non-interactive shell script)[1], it > installs following binaries in default PATH, > > cd, if, exec, wait, > > Some facts: > * These names are other shells built-in, but in execline

Re: Bug#906250: ITP: execline -- small and non-interactive scripting language

2018-09-01 Thread Shengjing Zhu
Dear -devel, When I try to package execline(a non-interactive shell script)[1], it installs following binaries in default PATH, cd, if, exec, wait, Some facts: * These names are other shells built-in, but in execline these are binaries. * There's no conflict binary name in archive currently

Bug#906250: ITP: execline -- small and non-interactive scripting language

2018-08-15 Thread Shengjing Zhu
Package: wnpp Severity: wishlist Owner: Shengjing Zhu Control: block 733915 by -1 Control: block -1 by 906200 * Package name: execline Version : 2.5.0.1 Upstream Author : Laurent Bercot * URL : https://skarnet.org/software/execline/ * License : ISC Programmi