All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: perl-native, why again?
Date: Tue, 15 Jun 2010 15:15:51 -0700	[thread overview]
Message-ID: <4C17FB97.1080505@mentor.com> (raw)

Hey all,

I was wondering, is there a reason for perl native aside from cpan?  If 
no, have we tried setting things up such that system perl uses a local 
to $TMPDIR cpan install spot?

I ask since once perl-native exist, stuff can get very unfun (too long 
#!/path/to/perl isn't fun at all).

Thanks.

-- 
Tom Rini
Mentor Graphics Corporation



             reply	other threads:[~2010-06-15 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 22:15 Tom Rini [this message]
2010-06-16  7:13 ` perl-native, why again? Koen Kooi
2010-06-16 15:15   ` 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=4C17FB97.1080505@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.