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
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
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
* 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
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
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
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
7 matches
Mail list logo
