On Wed, 21 Nov 2018 18:29:59 +0100 Alessandro Selli <alessandrose...@linux.com> wrote:
> On 21/11/18 at 18:21, Rowland Penny wrote: > > On Wed, 21 Nov 2018 18:05:44 +0100 > > Alessandro Selli <alessandrose...@linux.com> wrote: > > > >> On 21/11/18 at 17:57, Rowland Penny wrote: > >>> On Wed, 21 Nov 2018 17:43:12 +0100 > >>> Alessandro Selli <alessandrose...@linux.com> wrote: > >>> > >>>> On 21/11/18 at 17:37, Rowland Penny wrote: > >>>>> On Wed, 21 Nov 2018 17:28:40 +0100 > >>>>> Alessandro Selli <alessandrose...@linux.com> wrote: > >>>>> > >>>>>> On 21/11/18 at 17:22, Dr. Nikolaus Klepp wrote: > >>>>>>> Am Mittwoch, 21. November 2018 schrieb Hendrik Boom: > >>>>>> [...] > >>>>>> > >>>>>> > >>>>>>>> I read the discussion at > >>>>>>>> https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1642443.html > >>>>>>>> and it looks as if they fixed the discrepancy at version > >>>>>>>> 3.5.1-2. Which means if we want to keep sed in /bin instead > >>>>>>>> of /usr/bin we may have to patch both packages sed and > >>>>>>>> r-base. > >>>>>>>> > >>>>>>>> Or maybe add a symblic link to make sed accessible > >>>>>>>> from /usr/bin instead of just /bin. > >>>>>>> Why would anybody hardcode the link to sed in the first place? > >>>>>>> Isn't that what $PATH is all about? > >>>>>> It's necessary to keep script shebangs from breaking. > >>>>>> > >>>>> No it isn't, ever heard of 'which' or 'type' or checking if the > >>>>> file actually exists. > >>>>> > >>>>> Rowland > >>>>> > >>>> Of course it is. If you have a file with a shebang like this: > >>>> > >>>> > >>>> #!/bin/sed > >>>> > >>>> , which is the norm, see: > >>>> > >>>> https://github.com/uuner/sedtris/blob/master/sedtris.sed > >>>> > >>>> , then you'd be in trouble if sed moved in /usr/bin. > >>> Well it would if you were trying to run sed directly, > >> > >> Which side of "sed script with a shebang" do you fail to grasp? > > And which part of 'that isn't the problem' do you fail to grasp ? > > > You asked: > > > From: "Dr. Nikolaus Klepp" <dr.kl...@gmx.at> > To: dng@lists.dyne.org > Date: Wed, 21 Nov 2018 17:22:00 +0100 > Message-Id: <201811211722.00535.dr.kl...@gmx.at> > > > "Why would anybody hardcode the link to sed in the first place? Isn't > that what $PATH is all about?" > > > I answered to this question. > > > > From the debian bug report: > > > I did not answer any question about Debian bug reports, I answered > to the afore-quoted question. > > The Debian bug report is related anyway, because (though you didn't > know it) R itself can and in fact is used as a scripting language. > 'R' itself is a bash script and it hard codes the path to sed in it, this is, IMO, a stupid idea and lead to the problem when sed was moved. Rowland _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
