On Wed, 16 Apr 2008 19:17:51 +0200
Frank Gruellich <[EMAIL PROTECTED]> wrote:
> I was not able to create a filename or path containing it. (Anyone
> else?)
Unix file names can't contain / or null.
> Unfortunately that stupid sed does not work with \x00 as
> delimiter...
Nor do most Unix apps, s
* Marius Mauch <[EMAIL PROTECTED]> 15. Apr 08:
> On Tue, 15 Apr 2008 16:17:54 +0200
> Frank Gruellich <[EMAIL PROTECTED]> wrote:
> > * Santiago M. Mola <[EMAIL PROTECTED]> 15. Apr 08:
> > > On Tue, Apr 15, 2008 at 1:14 PM, Marijn Schouten (hkBst)
> > > Currently is use ':' as sed delimiter when pat
On Tuesday 15 April 2008, Marijn Schouten (hkBst) wrote:
> Hi list,
>
> it seems I have been using some fragile sed expression and I'd like to tap
> the collective wisdom for avoiding doing that in the future.
>
> dev-scheme/slib-3.1.5-r1 currently does
>
> sed "s_prefix = /usr/local/_prefix = ${D}
On Tue, 15 Apr 2008 16:17:54 +0200
Frank Gruellich <[EMAIL PROTECTED]> wrote:
> * Santiago M. Mola <[EMAIL PROTECTED]> 15. Apr 08:
> > On Tue, Apr 15, 2008 at 1:14 PM, Marijn Schouten (hkBst)
> > Currently is use ':' as sed delimiter when paths are involved. I'd
> > also like to hear from you abou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Petteri Räty wrote:
| You should just fix the Makefile to respect DESTDIR and send the patch
| upstream.
You're right of course, but that is only the right way for this specific
instance and not
a general way of handling tricky sed expressions.
Mar
Marijn Schouten (hkBst) kirjoitti:
Hi list,
it seems I have been using some fragile sed expression and I'd like to
tap the collective
wisdom for avoiding doing that in the future.
dev-scheme/slib-3.1.5-r1 currently does
sed "s_prefix = /usr/local/_prefix = ${D}/usr/_" -i Makefile
to make it
* Santiago M. Mola <[EMAIL PROTECTED]> 15. Apr 08:
> On Tue, Apr 15, 2008 at 1:14 PM, Marijn Schouten (hkBst)
> Currently is use ':' as sed delimiter when paths are involved. I'd
> also like to hear from you about proper delimiters if you think ':' is
> not safe enough.
>
> AFAIK, the only corner
> On Tue, 15 Apr 2008, Marijn Schouten (hkBst) wrote:
> There are several option to handle this. I could use a less common
> delimiter or I could escape it: ${D//_/\_} instead of ${D}. I could
> use a sed expression that doesn't suffer from this problem (thanks
> to dleverton):
> sed -ne '\_^
On Tuesday 15 April 2008 12:14:57 Marijn Schouten (hkBst) wrote:
> There are several option to handle this. I could use a less common
> delimiter or I could escape it: ${D//_/\_} instead of ${D}. I could use a
> sed expression that doesn't suffer from this problem (thanks to dleverton):
>
> sed -ne
On 15-04-2008 13:05:26 +0200, Santiago M. Mola wrote:
> On Tue, Apr 15, 2008 at 1:14 PM, Marijn Schouten (hkBst)
> <[EMAIL PROTECTED]> wrote:
> >
> > Hi list,
> >
> > it seems I have been using some fragile sed expression and I'd like to tap
> > the collective
> > wisdom for avoiding doing that
On Tue, Apr 15, 2008 at 1:14 PM, Marijn Schouten (hkBst)
<[EMAIL PROTECTED]> wrote:
>
> Hi list,
>
> it seems I have been using some fragile sed expression and I'd like to tap
> the collective
> wisdom for avoiding doing that in the future.
>
> dev-scheme/slib-3.1.5-r1 currently does
>
> sed "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi list,
it seems I have been using some fragile sed expression and I'd like to tap the
collective
wisdom for avoiding doing that in the future.
dev-scheme/slib-3.1.5-r1 currently does
sed "s_prefix = /usr/local/_prefix = ${D}/usr/_" -i Makefile
12 matches
Mail list logo
