Re: [Ceps-discuss] pswatch, perl-paths and the build

[Adam C. <ab...@pr...>]

On Wed, 29 Jan 2003, Robert Lehr wrote:

> On Wed, Jan 29, 2003 at 09:06:27PM -0800, Adam Crews wrote:
> > I'd like to see autoconf use psconfig if it's available, and of course
> > allow anyone to override the psconfig results with command line options.
> >
>
> I want to loosen the binding between compilation and script configs,
> not tighten it.  Just get the compilation parameters out of the scripts
> themselves.
>
> I suspect that you have another intent, though.  Perhaps having the build
> guess at the configuration based on the configuration of the CEPS server
> on which the build is executing?  That would be useful as long as the
> configs go into 'psconfig' instead of the scripts themselves.
>

I totally agree that this should be loosened.  I think most if not all the
scripts can be updated so that the path to psconfig is the only hard coded
path, (or make sure that psconfig is in a usual system path such as
/usr/bin).  Then all the scripts get the location of things like the spool
directory and such out of the psconfig results.  I have done this with
many of the scripts I am using now.

--snip--

>
> Thanks a lot, Adam.  That's pretty cool.  If only it was in a separate
> module that all perl scripts could load from /etc/ceps or something like
> that.  Then the scripts can find remaining CEPS scripts based on the
> configuration pulled from this sub.
>
> Robert Lehr
>
>


The PrintHTML.pm that I am using has been modified a bunch and is probably
a good start for a central CEPS perl module.  It basically combines the
PrintNDS and PrintHTML modules together, and adds a few more functions.
The PrintNDS module had a basic sddb interface.  It simply did the shell
escapes to do the proper sddb calls.

I also started using the CGI.pm module for most html stuff.  It makes the
code easier to read without all the html markup all over.  It also has
some very nice functions for generating tables and forms.

Don't laugh at my perl code in there, it needs some work, but it does the
job for now.  I'll do a re-write of it some time soon here.  I'd love to
see a real perl interface to sddb to replace a bunch of this though.

-Adam