Re: P5EEx::Blue ready for alpha users

Hi,

Glad to work with you.

At 12:15 AM 3/23/2002 +0100, Valerio_Valdez Paolini wrote:
....
>I will be very happy to contribute to your work, even if only as
>tester, but preferably coding something useful. Unfortunately,
>many concepts are new to me, so i may need some help to clarify
>how your meta-framework works, what is behind it and some general
>clues about the preferred way to do something.
>
>I also must admit that my english is not good (i'm italian), so
>please be patient :) 

We'll do our best to communicate.

>On Tue, 19 Mar 2002, Stephen Adkins wrote:
>
>> If there is anyone interested in downloading, installing, and
>> configuring this for use, I will be happy to work with you
>> and get feedback.
>
>I downloaded the latest version, marked p5ee_2002-03-22_140003,
>and found this:
>
># perl Makefile.PL
>Checking if your kit is complete...
>Warning: the following files are missing in your kit:
>        sbin/perldocs
>Please inform the author.
>Writing Makefile for P5EEx-Blue

The file is renamed from "sbin/perldocs" to "sbin/perldocs.PL".
You can change it directly in your MANIFEST.
I have updated the CVS repository, and soon there will be a new
snapshot.

>may be it is not important, but you asked to be informed. On my red hat
>7.2 with perl 5.6.0, perldoc is located under /usr/bin. However the
>installation finished without errors.
>
>May I suggest to ask where to install 'web parts', instead of assuming
>/usr/local as default destination? I have too many things in usr/local
>to place all there without risk of confusion (openssl, netscape plugins
>and so on).
>
>I'm looking at documentation, and found that all html files have broken
>links; I resolved changing /pub/p5ee/software/htdocs/ to /P5EEx-Blue/

I recommend you choose a "development PREFIX" instead of "/usr/local".
I use "/usr/ov/acoc/devel".  You might use "/home/paolini/devel"
or something.  Set the PREFIX environment variable in your ".profile"

  PREFIX=/home/paolini/devel; export PREFIX

unpack the distribution under $PREFIX/src.
Then to build it, make sure that PREFIX is set and do ...

  cd $PREFIX/src/p5ee/P5EEx/Blue
  perl Makefile.PL
  make
  make install

This will keep things out of /usr/local.
It also sets you up to have different $PREFIX vars for different
versions of the software from development through production.

As for the broken links, see if there is a reasonable way for you
to make symbolic links from the Apache "htdocs" and "cgi-bin"
directories to the target directories under the PREFIX directory.

>I don't know where to start to try something; the scripts in cgi-bin
>has some errors (p5x complains about "create(): no config file specified
>or found"; ttx can't find Template.pm, wich one should be used? there is
>also a missing ; at line 88 ::Widget::HTML::Template).

1. Whatever URL you used to access p5x, add "/demo/report" to the end of it.
   This will help it find the "demo_report.conf" and "demo_report.pl"
   config files.
2. "ttx" is for driving Template Toolkit.
   You would need to get that from CPAN, but this tool is recommended but
   not necessary.
3. The semicolon syntax error has been fixed.

>I think i should try first to make your examples work, right? Can you
>give me some hints please?

see above.

>The last question, what did you use to generate all the html documentation
>or, if you prefer, what is the developing methodology behind it?

I used "perldocs" (not to be confused with "perldoc" which comes with Perl).

Stephen