On Fri, 20 May 2011 17:39:22 +0200
Jeroen Roovers wrote:
> for a while now I've been wondering if all those sed scripts in all
> those ebuilds are really effective.
This took rather long to find some spare time for.
Plonk the attached bash script into /etc/portage/bashrc.d (which you
source in
On Sunday 29 May 2011 13:00:32 Fabian Groffen wrote:
> On 29-05-2011 12:44:46 +0200, Christopher Schwan wrote:
> > Thank you for that script. I experimented a bit with it and have a number
> > of corrections and suggestions:
> >
> > - alias does not work because my_sed is not declared at this stag
On 29-05-2011 12:44:46 +0200, Christopher Schwan wrote:
> Thank you for that script. I experimented a bit with it and have a number of
> corrections and suggestions:
>
> - alias does not work because my_sed is not declared at this stage. I removed
> the whole alias line because I want to selecti
Thank you for that script. I experimented a bit with it and have a number of
corrections and suggestions:
- alias does not work because my_sed is not declared at this stage. I removed
the whole alias line because I want to selectively enable my_sed
- oargs must be an array in order to make quoti
On 21-05-2011 19:34:34 +0200, Jeroen Roovers wrote:
> On Fri, 20 May 2011 17:56:00 +0200
> Fabian Groffen wrote:
>
> > sed -e "" "${file}" | diff "${file}" -
> >
> > followed by the actual sed -i -e ...
> >
> > This way I didn't need to write an intermediate file.
>
> The problem there is th
On Fri, 20 May 2011 17:56:00 +0200
Fabian Groffen wrote:
> sed -e "" "${file}" | diff "${file}" -
>
> followed by the actual sed -i -e ...
>
> This way I didn't need to write an intermediate file.
The problem there is that sed might be called just once on any one file,
but in the tree it is
On 20-05-2011 17:39:22 +0200, Jeroen Roovers wrote:
> I've looked into sed's internal solutions to no avail, but something
> like -i[SUFFIX] might help, since it gives you a backup file to compare
> with the file that's being streamed.
>
> The idea is to pass the result to
> | diff -u $file $fil
Hullo developers,
for a while now I've been wondering if all those sed scripts in all
those ebuilds are really effective.
To find out, I've tried a couple of angles on a sed hook that basically
dissects the sed command line provided, divides everything up into sed
scripts, files being proc
