Re: [Nms-cgi-devel] more moving somewhere...

[Nick C. <ni...@cl...>]

On Tue, Jan 21, 2003 at 05:57:05AM -0500, Wizard wrote:
> 1.> per Nick's modules, why do we have to inline modules? why not create a
> local /lib/dir and use libs? This way, if modules end up being shared
> between NMS scripts, were not duplicating efforts/installs (and you only
> have to update them once). We'll probably want a separate CVS tree, though.

The local /lib/dir approach is better, for all the reasons you state.

However, we're aiming to provide plugin replacements for Matt's scripts,
and some users can't or won't upload a load of .pm files to a web
server, so we need standalone scripts.

Here's a plan to get the best of both worlds:

In CVS, we will use the local lib dir approach.  We will think in terms
of a local lib dir when writing the scripts and modules.  At release
time, we will release a package of the script with all its modules as
separate files, to go in a local lib dir.  That's almost done for
FormMail, see /v2/packages/formmail_modules/ in CVS.

To accommodate those users who insist that they want to upload a
standalone script (and take the efficiency and maintenance hit), at
every release a perl script will generate a version of the package with
all the modules it needs inlined into the CGI.  I've just started on
this for FormMail in /v2/packages/formmail_compat/ in CVS.
 
> 4.> What the hell am I supposed to be doing with WWWBoard (so far the only
> thing that I've done is add a stylesheet and a no-cache pragma)? I would
> like to modularize it, but I find myself asking 'why?' if we are just
> inlining it.

Well, I'd leave the existing wwwboard as it is apart from bug fixes,
and maybe look at starting on a de-inlined version under /v2.

--
Nick