On Fri, Jun 26, 2015 at 06:18:57PM -0500, Bruce Dubbs wrote:
>
> Try this:
>
> sed -i -e 's/ GST_CHECK_FAAD_VERSION / /' \
> -e '/"GST_CHECK_FAAD_VERSION/{
> s/GST_CHECK_FAAD_VERSION //
> s/""/"$"/ }' configure
>
> It an interesting sed because there are two substitutions on one line.
> The format of the second expression is:
>
> /address/{
> instruction1
> instruction2}
>
> The address here is a simple match on the line.
>
> There is only one entry in the file where GST_CHECK_FAAD_VERSION has a space
> both before and after. There is only one place in the file where
> GST_CHECK_FAAD_VERSION is preceded with a " character.
>
> I think this is relatively clear if you know how to read a sed. There are
> no escapes and no regexes. [Well, text is technically a regex. :) ]
>
> -- Bruce
>
Thanks. I'll give it a go, but maybe not for a day or three. I
think I've now understood the explanation. I must admit that I
wasn't thinking about escapes on my first attempt - the second line
didn't get changed, so maybe my working version had more than it
needed.
At the moment my brain is addled from looking at my biber/perl notes,
and I've found an apparently-required set of extra deps (for testing
a dependant module) where the module does not seem to have changed
its version. And I thought this week was bad (for non-blfs reasons)
*before* that fell out of my notes. Oh well, maybe I'll get eaten
by a mutant star-goat before I have to fix up the perl modules.
Meanwhile, would somebody pass me a pan galactic gargle blaster,
please ? ;-)
ĸen, definitely B Ark material :-(
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
