Nikolaus Rath writes ("Re: bash without importing shell functions from the
environment"):
> I think the latter. I was actually curious as well and checked. The
> wheezy version has custom debian/patches handling where e.g.
> debian/patches/series is processed by the C preproc
Matthias Klose writes:
> Am 25.09.2014 um 17:29 schrieb Ian Jackson:
>> (It took me merely a few moments with the source code to prepare the
>> code patch. But then I had to spend an hour or two wrestling with the
>> patch systems of the packages in squeeze and wheezy. I would like to
>> take th
On Tue, Sep 30, 2014 at 07:58:38PM +0200, Matthias Klose wrote:
> so maybe as a non-native speaker I am unaware of some joke here, or are you
> just
> trolling about something fixed for jessie/unstable?
I was curious to see what Ian was complaining about, and what has changed up to
the jessie ver
Am 25.09.2014 um 17:29 schrieb Ian Jackson:
> (It took me merely a few moments with the source code to prepare the
> code patch. But then I had to spend an hour or two wrestling with the
> patch systems of the packages in squeeze and wheezy. I would like to
> take this opportunity to say how much
Joey Hess writes ("Re: bash without importing shell functions from the
environment"):
> Jonathan Dowland wrote:
> > Thank you very much for doing this. I would love to see Debian
> > transition to having this facility disabled by default at some
> > point in th
Jonathan Dowland wrote:
> Thank you very much for doing this. I would love to see Debian transition to
> having this facility disabled by default at some point in the future.
Florian Weimer's patch doesn't go that far, instead environment
variables have to have special BASH_FUNC_FOO() names before
On Thu, Sep 25, 2014 at 04:29:05PM +0100, Ian Jackson wrote:
> I have prepared bash packages which do not honour any shell functions
> they find in the environment. IMO that is a crazy feature, which
> ought to be disabled. (I'm running this on chiark now and nothing has
> visibly broken yet.)
T
Juliusz Chroboczek wrote:
Just to make things clear -- you're advocating #!/bin/sh and running
dash
as /bin/sh?
(Likely alternatives include at least ksh and mksh, formerly pdksh.)
I think this has already happened wherever it was easy. So to
remove /bin/bash sc
On Thu, 25 Sep 2014, shawn wilson wrote:
> In that case, I'd think busybox's sh is *much* more minimalist. Why dash
> over busybox?
There is something called bugs. The busybox implementation
is artificially limited. Also, it uses the busybox common
code, which makes its codebase rather large.
Th
shawn wilson writes:
> On Sep 25, 2014 9:36 PM, "Russ Allbery" wrote:
>> That may be overkill, but I will say that I'm feeling *extremely*
>> grateful the last few days that we pushed forward with switching
>> /bin/sh to dash, even though some folks thought this was a bad idea.
>> Having the she
On Sep 25, 2014 9:36 PM, "Russ Allbery" wrote:
>
> Josselin Mouette writes:
>
> > Since I’m pretty sure we haven’t uncovered all of bash’s “features”,
> > wouldn’t it be a good opportunity to make a release goal of killing all
> > scripts with a #!/bin/bash shebang?
>
> That may be overkill, but
Josselin Mouette writes:
> Since I’m pretty sure we haven’t uncovered all of bash’s “features”,
> wouldn’t it be a good opportunity to make a release goal of killing all
> scripts with a #!/bin/bash shebang?
That may be overkill, but I will say that I'm feeling *extremely* grateful
the last few
> Since I’m pretty sure we haven’t uncovered all of bash’s “features”,
> wouldn’t it be a good opportunity to make a release goal of killing all
> scripts with a #!/bin/bash shebang?
Just to make things clear -- you're advocating #!/bin/sh and running dash
as /bin/sh?
(Likely alternatives include
Le jeudi 25 septembre 2014 à 16:29 +0100, Ian Jackson a écrit :
> I have prepared bash packages which do not honour any shell functions
> they find in the environment. IMO that is a crazy feature, which
> ought to be disabled. (I'm running this on chiark now and nothing has
> visibly broken yet.)
Hi Ian,
On Thu, September 25, 2014 17:29, Ian Jackson wrote:
> I have prepared bash packages which do not honour any shell functions
> they find in the environment. IMO that is a crazy feature, which
> ought to be disabled. (I'm running this on chiark now and nothing has
> visibly broken yet.)
15 matches
Mail list logo
