[31919] in Perl-Users-Digest
Perl-Users Digest, Issue: 3182 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Oct 19 06:09:19 2010
Date: Tue, 19 Oct 2010 03:09:05 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 19 Oct 2010 Volume: 11 Number: 3182
Today's topics:
Re: CGI, multiple page data input. <justin.1010@purestblue.com>
Re: CGI, multiple page data input. <justin.1010@purestblue.com>
Like to meet Hot women on cam and chattin FREE?! Check <tallboymonster@gmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: where to install cpan modules <john@example.invalid>
Re: where to install cpan modules <john@example.invalid>
Re: where to install cpan modules <nospam-abuse@ilyaz.org>
Re: where to install cpan modules <merrilljensen@q.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 19 Oct 2010 10:29:57 +0100
From: Justin C <justin.1010@purestblue.com>
Subject: Re: CGI, multiple page data input.
Message-Id: <l150p7-s78.ln1@zem.masonsmusic.co.uk>
On 2010-10-18, Mathematisch <mathematisch@gmail.com> wrote:
>
> Try using: CGI::Session
Thank you. I have the documentation for this open and it looks
interesting. It looks like a whole new can of worms compared with my
very basic web programming.
Justin.
------------------------------
Date: Tue, 19 Oct 2010 10:32:11 +0100
From: Justin C <justin.1010@purestblue.com>
Subject: Re: CGI, multiple page data input.
Message-Id: <r550p7-s78.ln1@zem.masonsmusic.co.uk>
On 2010-10-18, Jürgen Exner <jurgenex@hotmail.com> wrote:
> Justin C <justin.1010@purestblue.com> wrote:
>>All of my web stuff (inhouse) until now has passed previously input data
>>back to the browser in hidden form fields when more data needs to be
>>collected. For example, my script that calculates shipping rates for
>>customer orders collects weight, number of items, country of destination
>>on the first page. When this page is submitted a new page is returned
>>asking for the dimensions of each box, this second page form is
>>dependent on input from the first page (each box can be different
>>dimensions), but I also need some of the original page's input for my
>>calculations later, so the original data is passed back in hidden form
>>fields.
>>
>>I'd like to move my coding forward a little and find a better way. I'm
>>guessing the cookies is the correct way to progress with this, but I
>>want to be sure, or hear of other ways before I commit to a cookies
>>approach for my new web-page.
>
> You are looking for sessions.
Yes, I see that now.
> Of course this has nothing to do with Perl whatsoever because the
> concept of sessions is totally independent of whatever programming
> language you happen to be using to implement them.
ISWYM... now I know what it is that that I'm asking!
Justin.
------------------------------
Date: Mon, 18 Oct 2010 21:40:24 -0700 (PDT)
From: jack daniels <tallboymonster@gmail.com>
Subject: Like to meet Hot women on cam and chattin FREE?! Check this out!
Message-Id: <459ecb93-79be-4327-ba5e-87e524534515@a36g2000yqc.googlegroups.com>
Check out Fubar, the only online bar and happy hour! Rate, chat, and
cam over 5 million people! Make friends or just play the game. Like
Facebook? Give Fubar a try. Follow this link as joining is by
invitation only. http://www.fubar.com/join_w1.php?friend=2393742
------------------------------
Date: Tue, 19 Oct 2010 02:05:54 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <yKGdnZCH-7vP3iDRnZ2dnUVZ5rqdnZ2d@giganews.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Mon, 18 Oct 2010 23:06:33 -0600
From: John Smith <john@example.invalid>
Subject: Re: where to install cpan modules
Message-Id: <POidnS_omITHuiDRnZ2dnUVZ5umdnZ2d@giganews.com>
J. Gleixner wrote:
[snip]
> Learn how to use CPAN. perldoc CPAN and/or perldoc perlmodinstall
> or look online for how to use it. Usually you configure it once,
> and then you do the same thing to install a module every time.
I did read as much of that as I could. It's very long, and not a whole
lot sinks in at first reading.
I've been doing the things that the cpan interactive suggests, more or
less, and I seem to be able to command
cpan Module::Name
and have everything I need to build that module arrive in
/home/ron/.cpan/build/
Thereafter, I have to go in there, open a terminal in the base directory
(that which postpends the above), and run
perl Makefile.PL
...
make install
I thought I read that the cpan command has the ability to do all this
last stuff too, but I didn't see a usage, which are few and far between
in man documentation.
This also seems like a good candidate for a script.
>> Is there a way with a browser on CPAN to download a module along with
>> its dependencies without having to chase them down?
>
> CPAN does that for you, so stop trying to use a browser to do anything,
> unless you find something that isn't in CPAN. Your OS might also have
> a package manager, e.g. yum, rpm, etc. If so, maybe that's what you
> should be using instead of CPAN. It depends on how you manage what's
> installed on your system.
Thx, j., I took a look at this:
http://i55.tinypic.com/21pyc2.png
It looks to be a python thing to me. Since I got Python::Inline
wrangled, I'm fine with leaving things as they are right now.
I didn't want to sound like this guy:
http://www.perlmonks.org/?node_id=840076
Cheers,
--
John Smith
------------------------------
Date: Mon, 18 Oct 2010 23:30:40 -0600
From: John Smith <john@example.invalid>
Subject: Re: where to install cpan modules
Message-Id: <ye2dnRBpPYOYsCDRnZ2dnUVZ5qidnZ2d@giganews.com>
Ben Morrow wrote:
> That message would be better worded 'Perl's config says that U32 access
> does not have to be aligned', and it's not a warning, simply a piece of
> information. (In general, if a Makefile.PL succeeds in producing a
> Makefile it worked.)
Ok, I guess I was reading this with pessimism:
$ perl Makefile.PL
Perl's config says that U32 access must not be aligned.
Checking if your kit is complete...
Looks good
Writing Makefile for Digest::MD5
$
(I read, "...must not be aligned, because something sure is screwed up.")
>
> U32 is the perl name for an unsigned 32bit integer, which is a quantity
> used a lot calculating MD5s. Some processors (Sparc and I think PPC in
> particular) require any C code manipulating U32s to be sure to keep them
> aligned in memory: that is, since a U32 is four bytes long, each U32
> must start at an address that is a multiple of four. Some, like the
> Intel processors, do not. Digest::MD5 is simply checking how careful it
> needs to be in the C part of the code, and telling you what it found
> (just in case you care :) ).
C is a fickle mistress, but I always care.:-)
--
John Smith
------------------------------
Date: Tue, 19 Oct 2010 08:44:03 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: where to install cpan modules
Message-Id: <slrnibqmij.3b6.nospam-abuse@powdermilk.math.berkeley.edu>
On 2010-10-18, Justin C <justin.1010@purestblue.com> wrote:
> On 2010-10-17, Ilya Zakharevich <nospam-abuse@ilyaz.org> wrote:
>> On 2010-10-16, John Smith <john@example.invalid> wrote:
>>> Einstein defined insanity as doing the same thing repeatedly and
>>> expecting different results.
>>
>> Each time I try to define insanity, I get different results... Now whta?
>
> You must be doing it wrong, please post an example of your code :)
>
> #!/usr/bin/perl
>
> use strict;
> use warnings;
>
> my $insanity = "true";
>
> die "\$insanity undefined" unless defined $insanity;
>
> __END__
All this shows is that there is some dollar value in insanity...
Ilya
------------------------------
Date: Tue, 19 Oct 2010 03:05:03 -0600
From: Uno <merrilljensen@q.com>
Subject: Re: where to install cpan modules
Message-Id: <87WdndWhmO6iwiDRnZ2dnUVZ5h2dnZ2d@giganews.com>
[warning: long post]
Ben Morrow wrote:
> Quoth John Smith <john@example.invalid>:
> Proclaiming one's superiour knowledge is one of the primary functions of
> Usenet. It's not wise to take offence at it. Also, questions about
> general Unix usage that do not pertain directly to using Perl are OT
> here, and likely to be badly received.
[x-posted to c.u.p.]
The material that I have worked up for unix usage has previously been on
my main ubuntu identity, who posts as "Uno." Ergo, OP is posting as
"John Smith" and "Uno," and has crossposted to the best place he knows
to talk about unix.
I have more tools over here than I do with my fledgling install, and I
thought I could avail myself of them by maximizing group priveleges, as
both of my users belong to the same group:
$ pwd
/home/dan
$ ls -ald source
drwxr-xr-x 13 dan dan 4096 2010-10-06 02:47 source
$ sudo chmod g=wrx source
[sudo] password for dan:
$ ls -ald source
drwxrwxr-x 13 dan dan 4096 2010-10-06 02:47 source
$ cd source
$ ls
9vx-0.12 g1.c~ p7.c~
a1.c g2.c p8.c
...
f_pi2.f90~ p6.c~ unleashed
g1.c p7.c Unsaved Document 1
$ ls -ald
drwxrwxr-x 13 dan dan 4096 2010-10-06 02:47 .
$ ls -ald a*
-rw-r--r-- 1 dan dan 198 2010-09-01 17:27 a1.c
-rw-r--r-- 1 dan dan 198 2010-09-01 17:26 a1.c~
-rw-r--r-- 1 dan dan 811 2010-09-20 19:55 a1.F90
-rw-r--r-- 1 dan dan 1014 2010-09-22 15:37 a2.F90
-rw-r--r-- 1 dan dan 1014 2010-09-21 21:17 a2.F90~
drwxr-xr-x 2 dan dan 4096 2010-05-29 13:47 amd64
-rwxr-xr-x 1 dan dan 9188 2010-09-22 15:46 a.out
drwxr-xr-x 32 dan dan 12288 2010-10-18 23:56 apue.2e
$
Is there a switch with chmod has that makes the command apply to
subdirectories?
>> I was thinking I'd pick up 5 titles:
>>
>> 1) Programmieren in Perl
>> 2) Learning Perl
>> 3) A C title to replace H&S V.
>
> I here that the only correct book to learn C from is K&R. (I must
> confess I first learned C from a book called 'Using Microsoft Visual C++
> v1.0', but I hope I've forgotten most of it...)
K&R2 is, for me, a joyful psalm in 2 languages (including the proverbs
of _The C Answer Book_ by Tondo and Gimpel. (Mir ist neulich kundig,
dass es hiervon eine deutsche Ausgabe gibt.))
Willem's gentle flame provoked me to find _Running Linux_, which seems
to have a lot of good material from the user's perspective.
Fishing for another good unix title.
>
>> $ ls -ald perl*
>> drwxr-xr-x 3 root root 4096 2009-04-20 07:59 perl
>> drwxr-xr-x 38 root root 4096 2010-10-06 17:15 perl5
>> $ pwd
>> /usr/share
>> $
>>
>> Am I correct to think that execution went through the above directory 2
>> weeks ago and now goes through the below directory?
>
> No. Perl will (probably) search both directories when looking for a
> module. You can see which directories perl searches, and in what order,
> with
>
> perl -le'print for @INC'
Cool, cool. Interesting things here:
$ perl -V
Summary of my perl5 (revision 5 version 10 subversion 0) configuration:
Platform:
osname=linux, osvers=2.6.24-23-server,
...
Built under linux
Compiled at Jun 26 2009 18:23:00
@INC:
/etc/perl
/usr/local/lib/perl/5.10.0
/usr/local/share/perl/5.10.0
/usr/lib/perl5
/usr/share/perl5
/usr/lib/perl/5.10
/usr/share/perl/5.10
/usr/local/lib/site_perl
.
$ perl -le'print for @INC'
/etc/perl
/usr/local/lib/perl/5.10.0
/usr/local/share/perl/5.10.0
/usr/lib/perl5
/usr/share/perl5
/usr/lib/perl/5.10
/usr/share/perl/5.10
/usr/local/lib/site_perl
.
$
I notice the same files and order and disbelieve the coincidence both on
first inspection and presently.
>
>> What happens on unix when one commands
>> perl anything
>
> How much detail do you want?
>
> In simple terms: the shell tells the kernel to execute 'perl anything';
> the kernel starts perl, passing it the command line; perl opens the file
> 'anything' and reads it; perl compiles the Perl in the file; perl
> executes the compiled program. If the program contains a 'use' or
> 'require' statement, perl will look for the named module or file in each
> directory in @INC, in order.
Right at the head of @INC is etc/perl, and I think this a useful read:
$ ls
CPAN Net
$ cd CPAN
$ ls
Config.pm Config.pm~
$ cat Config.pm
# This is CPAN.pm's systemwide configuration file. This file provides
# defaults for users, and the values can be changed in a per-user
# configuration file. The user-config file is being looked for as
# ~/.cpan/CPAN/MyConfig.pm.
$CPAN::Config = {
'applypatch' => q[],
'auto_commit' => q[0],
'build_cache' => q[100],
'build_dir' => q[/root/.cpan/build],
'build_dir_reuse' => q[1],
'build_requires_install_policy' => q[ask/yes],
'bzip2' => q[/bin/bzip2],
'cache_metadata' => q[1],
'check_sigs' => q[0],
'commandnumber_in_prompt' => q[1],
'cpan_home' => q[/root/.cpan],
'curl' => q[],
...
'wget' => q[/usr/bin/wget],
'yaml_load_code' => q[0],
'yaml_module' => q[YAML],
};
1;
__END__
$ pwd
/etc/perl/CPAN
$
>
> Usually you would install modules that can be shared between machines in
> one directory and modules with compiled C components that cannot in
> another, to make it easier to share module directories on a network of
> different machines. Usually these directories are called something like
>
> /usr/local/lib/perl5/site_perl/5.12.2
> /usr/local/lib/perl5/site_perl/5.12.2/i386-freebsd-64int
>
> respectively, but many distribution-provided perls have added extra
> entries to @INC for /usr/lib/perl and /usr/share/perl since these fit in
> better with the various filesystem-hierarchy standards. Probably what
> has happened here is that since you installed some modules using the
> CPAN shell they went into the perl5 directory, but it's not clear what
> went in there or why from here.
I'm not sure what you mean here, Ben. Let me ask you a question.
I did a locate *pm command and found a sufficiently large number of
files that I would believe that they might not be unique.
What is the perl way of deciding which .pm is relevant?
--
Uno
John smith
Peace,
love,
John Lennon
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 3182
***************************************
