All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Disable packaged-staging for perl-native
Date: Wed, 28 Jul 2010 08:45:00 -0700	[thread overview]
Message-ID: <4C50507C.5050906@mentor.com> (raw)
In-Reply-To: <201007281128.37653.khimov@altell.ru>

Roman I Khimov wrote:
> В сообщении от Среда 28 июля 2010 03:45:21 автор Tom Rini написал:
>> I'd like to disable packaged-staging for perl-native.  The problem here
>> comes from a number of things that happen.  Some of these can only
>> happen in combination with packaged-staging but others I believe could
>> happen today.  The problem itself is that if we have perl-native
>> available from packaged-staging it can suddenly exist very early.  What
>> this means in practical terms is that now we're trying to generate say
>> pod2man.pl from pod2man.pl.in and @perl@ is expanded to something beyond
>> the "#!" mechanic length limit and recipes start failing to build
>> (fixable by changing pod2man.pl.in to use /usr/bin/env perl (and if it
>> had a -w changing to Use warnings: or whatever the perl is)).
> 
> So the problem really is that we have perl in /very-very-long-path/perl? IMO 
> /usr/bin/env change would be better in that case. 

The most common case is that one, yes.  I'm open to suggestions on 
catching and fixing these problems ahead of time but the issue is we're 
talking about for example wget which has no dependency on perl-native.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2010-07-28 15:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 23:45 [RFC] Disable packaged-staging for perl-native Tom Rini
2010-07-28  7:09 ` Koen Kooi
2010-07-28  7:28 ` Roman I Khimov
2010-07-28 15:45   ` Tom Rini [this message]
2010-08-12 17:12     ` Tom Rini
2010-08-12 17:29       ` Roman I Khimov
2010-08-12 19:00         ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C50507C.5050906@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.