public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Anderson <ryan@michonline.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: Perl in the toolchain
Date: Sat, 1 Feb 2003 01:02:27 -0500	[thread overview]
Message-ID: <20030201060227.GA29945@michonline.com> (raw)
In-Reply-To: <200302010106.h1116XP08674@devserv.devel.redhat.com>

On Fri, Jan 31, 2003 at 08:06:33PM -0500, Pete Zaitcev wrote:
> 
> For the record, the userland which I posess does have a somewhat
> working Perl RPM, which originates from Red Hat 5.2, I believe.
> So, I cannot invoke "missing perl" argument in good conscience.
> However, I shudder to think what happens if I need to rebuild it
> for some reason.

Well, do "perl -v" and see if it's at least 5.004 (5.004.003 I think
would be better.)  If so, hpa's requirement that everything work on
5.004 is fine.  (And really, I don't believe that requirement is going
to be hard to follow, except that it does constrain the modules in use a
little bit - I'm pretty sure the Digest::MD5 was missing from the 5.004
default set of modules.)

> There's also a subject of a skillset. I know nil about Perl.
> (ok, I hacked sirc long ago. I don't think it counts.)

If you hacked sirc...  Well, that's an example of incredibly bad Perl,
so, you should be able to follow well-written and documented Perl, imo.

(I did an amazing amount of sirc hacking in my time, and it was an
exercise in pain, to be honest.)


-- 

Ryan Anderson
  sometimes Pug Majere

  reply	other threads:[~2003-02-01  5:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-31 18:39 Perl in the toolchain Pete Zaitcev
2003-01-31 19:41 ` Kai Germaschewski
2003-01-31 19:48   ` Jeff Garzik
2003-01-31 19:55     ` Mr. James W. Laferriere
2003-01-31 20:41     ` Sam Ravnborg
2003-01-31 22:50       ` Ben Greear
2003-01-31 21:38     ` J.A. Magallon
2003-01-31 22:22       ` Sam Ravnborg
2003-01-31 23:23         ` Jeff Garzik
2003-02-01  0:29           ` H. Peter Anvin
2003-02-01 12:12           ` Sam Ravnborg
2003-01-31 23:40         ` J.A. Magallon
     [not found]         ` <mailman.1044055681.1939.linux-kernel2news@redhat.com>
2003-02-01  1:06           ` Pete Zaitcev
2003-02-01  6:02             ` Ryan Anderson [this message]
2003-01-31 22:51       ` Roman Zippel
2003-01-31 23:27       ` Jeff Garzik
2003-01-31 23:40         ` J.A. Magallon
2003-01-31 23:40           ` Jeff Garzik
2003-02-01  0:01           ` Roman Zippel
2003-02-01  0:05             ` J.A. Magallon
  -- strict thread matches above, loose matches on Subject: below --
2003-01-31 20:13 Ed Vance
2003-02-01  3:28 ` Scott Robert Ladd

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=20030201060227.GA29945@michonline.com \
    --to=ryan@michonline.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox