Re: ASH: why ash_ptr_to_globals_misc is declared as const pointer

On 30 Jan 2018 04:10, Denys Vlasenko wrote: > On Fri, Jan 26, 2018 at 8:39 PM, Yunlian Jiang wrote: > > I will use a similar issue in lineedit.c to explain the problem. (it is > > easier to reproduce). > > The problem is that > > clang thinks lineedit_ptr_to_statics is a

Re: [PATCH] ash: make bash_source command search current directory after PATH

On 30 Jan 2018 04:00, Denys Vlasenko wrote: > On Mon, Jan 29, 2018 at 7:50 PM, Mike Frysinger wrote: > >> I still wonder how on Earth Android filesystem ended up not having /bin/sh. > >> No one at Google realized that people are using shell scripts > >> all over the Unix universe? Or they

Re: ASH: why ash_ptr_to_globals_misc is declared as const pointer

On Fri, Jan 26, 2018 at 8:39 PM, Yunlian Jiang wrote: > I will use a similar issue in lineedit.c to explain the problem. (it is > easier to reproduce). > The problem is that > clang thinks lineedit_ptr_to_statics is a constant pointer, so the pointer > should be unchanged. As

Re: [PATCH] ash: make bash_source command search current directory after PATH

On Mon, Jan 29, 2018 at 7:50 PM, Mike Frysinger wrote: >> I still wonder how on Earth Android filesystem ended up not having /bin/sh. >> No one at Google realized that people are using shell scripts >> all over the Unix universe? Or they seriously did not want people >> to run

Re: [PATCH] ash: make bash_source command search current directory after PATH

On 29 Jan 2018 18:52, Denys Vlasenko wrote: > On Mon, Jan 29, 2018 at 5:55 PM, Mike Frysinger wrote: > >> >> >> I wish bash wouldn't introduce gratuitous standard violations. > >> >> > > >> >> > bash is its own shell. why can't it introduce its own extensions as > >> >> > it

Re: [PATCH] ash: make bash_source command search current directory after PATH

On Mon, Jan 29, 2018 at 5:55 PM, Mike Frysinger wrote: >> >> >> I wish bash wouldn't introduce gratuitous standard violations. >> >> > >> >> > bash is its own shell. why can't it introduce its own extensions as it >> >> > sees >> >> > fit ? >> >> >> >> Because a divergence is

Re: [PATCH 0/4] Add SCHED_BATCH and SCHED_IDLE support to chrt

Am 28.01.2018 19:23, schrieb Denys Vlasenko: > On Sun, Jan 28, 2018 at 11:10 AM, walter harms wrote: >>> On Wed, Jan 24, 2018 at 1:28 AM, Povilas Kanapickas >>> wrote: >> The following patches add SCHED_BATCH and SCHED_IDLE support to chrt. >> The

Re: [PATCH] ash: make bash_source command search current directory after PATH

On 29 Jan 2018 08:42, Paul Otto wrote: > On Sun, Jan 28, 2018 at 10:43 PM, Mike Frysinger wrote: > > On 28 Jan 2018 19:17, Denys Vlasenko wrote: > > > Making bash "source" behavior non-standard had nothing useful in it. > > > > "source" is already non-standard and not specified in POSIX. so

Re: [PATCH] ash: make bash_source command search current directory after PATH

On 29 Jan 2018 14:41, Denys Vlasenko wrote: > On Mon, Jan 29, 2018 at 6:43 AM, Mike Frysinger wrote: > > On 28 Jan 2018 19:17, Denys Vlasenko wrote: > >> On Fri, Jan 26, 2018 at 7:50 PM, Mike Frysinger wrote: > >> > On 26 Jan 2018 15:15, Denys Vlasenko wrote: > >> >> On Fri, Jan 26, 2018 at 9:34

Re: [PATCH] ash: make bash_source command search current directory after PATH

Thanks for the heads up, William! Great to hear! Thanks, Paul On Jan 29, 2018 8:49 AM, "William Pitcock" wrote: > Hello, > > On Sat, Jan 27, 2018 at 3:05 PM, Paul Otto wrote: > > Thanks for taking care of this, Denys. It didn't wind up the way I'd >

Re: [PATCH] ash: make bash_source command search current directory after PATH

Hello, On Mon, Jan 29, 2018 at 4:42 PM, Paul Otto wrote: > > > >> > Making bash "source" behavior non-standard had nothing useful in it. >> >> "source" is already non-standard and not specified in POSIX. so simply by >> using it, your script is not POSIX compliant. > > > That

Re: [PATCH] ash: make bash_source command search current directory after PATH

Hello, On Sat, Jan 27, 2018 at 3:05 PM, Paul Otto wrote: > Thanks for taking care of this, Denys. It didn't wind up the way I'd hoped, > but at least it is predictable both ways now. I will see if there is a way > to get Alpine Linux to build with that config option set, to

Re: [PATCH] ash: make bash_source command search current directory after PATH

I really want to argue that there is a quite simple workaround to get the bash 'source' behavior you need: Just append ":." to the PATH environment variable before you run the "." command. Or this: source () { PATH="$PATH:." . "$@" } Was there any difficulty of doing it?

Re: [PATCH] ash: make bash_source command search current directory after PATH

On Sun, Jan 28, 2018 at 10:43 PM, Mike Frysinger wrote: > On 28 Jan 2018 19:17, Denys Vlasenko wrote: > > On Fri, Jan 26, 2018 at 7:50 PM, Mike Frysinger wrote: > > > On 26 Jan 2018 15:15, Denys Vlasenko wrote: > > >> On Fri, Jan 26, 2018 at 9:34 AM, Paul Otto wrote: > > >> >

Re: [PATCH] ash: make bash_source command search current directory after PATH

On Mon, Jan 29, 2018 at 6:43 AM, Mike Frysinger wrote: > On 28 Jan 2018 19:17, Denys Vlasenko wrote: >> On Fri, Jan 26, 2018 at 7:50 PM, Mike Frysinger wrote: >> > On 26 Jan 2018 15:15, Denys Vlasenko wrote: >> >> On Fri, Jan 26, 2018 at 9:34 AM, Paul Otto wrote: >> >> > This