Loading ...
Sorry, an error occurred while loading the content.

Re: [PBML] View Source Code?????

Expand Messages
  • thehl1970
    CGI.pm appears to be an add-in module as my version of perl is 5.8.5. I can t speak to whether it should have been included as it appears not to be. And you re
    Message 1 of 14 , Jul 4, 2005
    • 0 Attachment
      CGI.pm appears to be an add-in module as my version of perl is 5.8.5.
      I can't speak to whether it should have been included as it appears
      not to be.

      And you're missing the point about speaking to the person who can
      change the files. I am selling shrink-wrap software. I have no control
      over the site it will be installed on. It will be installed by the ISP
      customer on the ISP's server. If I make my package dependent on an
      "optional" (regardless of how standard) package, then I end up doing
      tech support and playing broker between my client and their tech
      support. I can't think of a faster way to diminish the pleasure of
      running my own software company.

      I would really like to use the latest and greatest technologies, but
      it appears to be intractable in this situation unless someone can
      counsel me on how it can be done.

      Thanks!

      --- In perl-beginner@yahoogroups.com, "J.E. Cripps" <cycmn@n...> wrote:
      >
      > > If you can lend a hand as to how to deploy CGI.pm along with my
      > > application without modifying system files, I will adopt this as my
      > > long-term solution. If not, though, I feel I must continue to use the
      > > older cgi-lib.pl approach, as ugly as it is.
      >
      > Umm, if you don't have CGI.pm isn't your perl out
      > of date? Or something less than the standard installation?
      > Complain to whoever _can_ modify the system files.
      >
      > perldoc perlmodlib
      >
      > lists the those that are standard, and CGI is one.
      >
      > perldoc CGI
      >
      > should yield the documentation that comes with CGI.pm
      >
      > There's much more; there are entire books about CGI.pm
    • J.E. Cripps
      ... so is mine. What happens when you try perldoc CGI ... True but CGI.pm has been Standard for quite a while, and your client really should have it. I
      Message 2 of 14 , Jul 4, 2005
      • 0 Attachment
        > CGI.pm appears to be an add-in module as my version of perl is 5.8.5.
        > I can't speak to whether it should have been included as it appears
        > not to be.

        so is mine. What happens when you try

        perldoc CGI

        > If I make my package dependent on an "optional" (regardless of how
        > standard) package, then I end up doing tech support and playing broker
        > between my client and their tech support.

        True but CGI.pm has been "Standard" for quite a while, and
        your client really should have it. I mean, there were
        "Porting cgi-lib.pl Scripts to CGI.pm"
        http://search.cpan.org/src/LDS/CGI.pm-3.10/cgi-lib_porting.html
        written in 1998. AIUI, it's been around as long as Perl 5.
      • Mike Southern
        LOL! You should check out the cpan archives. They are full of perl modules sometimes so riddled with dependencies that the five minutes it takes to actually
        Message 3 of 14 , Jul 4, 2005
        • 0 Attachment
          LOL! You should check out the cpan archives. They are full of perl modules
          sometimes so riddled with dependencies that the five minutes it takes to
          actually perform the install is overwhelmed by the 3 hours it takes to find
          the correct required modules.

          That's a fact of perl development, it seems.

          It also seems your 5.8.5 may be missing something; CGI.pm is part of the
          standard package. Not optional.

          If you are using something else, then your package should indicate this -
          but before you do that I would seriously suggest that you find a machine
          that *does* use cgi.pm and test your package against that.

          If you are making an older function suite an install requirement, and there
          is a conflict between old and new then you really won't have a customer
          support problem at all; folk just won't use the software.

          > I would really like to use the latest and greatest technologies, but
          > it appears to be intractable in this situation unless someone can
          > counsel me on how it can be done.

          Not so sure it's latest and greatest. The module goes back to November 98.

          http://search.cpan.org/~lds/CGI.pm-3.10/

          I would counsel that you get yourself a fresh perl current download, install
          it, and test your application using cgi.pm



          On 7/4/05 7:08 PM, thehl1970 at thehl1970@... wrote:

          > CGI.pm appears to be an add-in module as my version of perl is 5.8.5.
          > I can't speak to whether it should have been included as it appears
          > not to be.
          >
          > And you're missing the point about speaking to the person who can
          > change the files. I am selling shrink-wrap software. I have no control
          > over the site it will be installed on. It will be installed by the ISP
          > customer on the ISP's server. If I make my package dependent on an
          > "optional" (regardless of how standard) package, then I end up doing
          > tech support and playing broker between my client and their tech
          > support. I can't think of a faster way to diminish the pleasure of
          > running my own software company.
          >
          > I would really like to use the latest and greatest technologies, but
          > it appears to be intractable in this situation unless someone can
          > counsel me on how it can be done.
          >
          > Thanks!
          >
          > --- In perl-beginner@yahoogroups.com, "J.E. Cripps" <cycmn@n...> wrote:
          >>
          >>> If you can lend a hand as to how to deploy CGI.pm along with my
          >>> application without modifying system files, I will adopt this as my
          >>> long-term solution. If not, though, I feel I must continue to use the
          >>> older cgi-lib.pl approach, as ugly as it is.
          >>
          >> Umm, if you don't have CGI.pm isn't your perl out
          >> of date? Or something less than the standard installation?
          >> Complain to whoever _can_ modify the system files.
          >>
          >> perldoc perlmodlib
          >>
          >> lists the those that are standard, and CGI is one.
          >>
          >> perldoc CGI
          >>
          >> should yield the documentation that comes with CGI.pm
          >>
          >> There's much more; there are entire books about CGI.pm
          >
          >
          >
          >
          > Unsubscribing info is here:
          > http://help.yahoo.com/help/us/groups/groups-32.html
          > Yahoo! Groups Links
          >
          >
          >
          >
          >
          >
        • Charles K. Clarkson
          ... You need to read more about modules and installing modules. I named the directory holding Template.pm HTML because the module is named HTML::Template. Look
          Message 4 of 14 , Jul 4, 2005
          • 0 Attachment
            thehl1970 <> wrote:

            : Evidently, there is a requirement to install CGI.pm. If you run
            : make install, it registers it's presence by modifying a file in
            : the perl interpreter directory. If you simply make the CGI.pm
            : and do not run the install, the copy the CGI.pm file into the
            : HTML directory, running a PERL program that accesses this
            : generates an error. If you move it to the same directory as your
            : script, same exact problem.

            You need to read more about modules and installing modules. I
            named the directory holding Template.pm HTML because the module is
            named HTML::Template. Look at the first line of that module.

            package HTML::Template;

            Since CGI.pm is not named HTML::CGI, perl will not look for it
            in the HTML directory. It would look for it in the current
            directory, which is probably /cgi-bin/.


            : If you can lend a hand as to how to deploy CGI.pm along with my
            : application without modifying system files, I will adopt this as
            : my long-term solution. If not, though, I feel I must continue to
            : use the older cgi-lib.pl approach, as ugly as it is.

            In your case I would change the directory hierarchy to this.

            /cgi-bin/
            MyScript.pl

            modules/
            CGI.pm

            CGI/
            Util.pm

            HTML/
            Template.pm

            In your scripts add the following near the top.

            use lib 'modules';

            Or (I didn't test):

            use lib './modules';

            In one IIS installation I use an absolute path.


            The Util.pm module above is needed by CGI.pm. At the top of
            that file is the following line. See how it works now?

            package CGI::Util;


            When using other modules mentally change the :: to / (or
            whatever your directory separator is). Install them using this
            directory structure.


            HTH,


            Charles K. Clarkson
            --
            Mobile Homes Specialist
            254 968-8328
          Your message has been successfully submitted and would be delivered to recipients shortly.