[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Mar 24 19:01:16 2000 
Subject:forwarding message from Steve Leach re Running Pop-11 
From:Aaron Sloman See text for reply address 
Volume-ID:1000324.01 

[To reply to Aaron replace "Aaron.Sloman.XX" with "A.Sloman"]

It looks as if Steve's message did not get through our Mail->News link.
In fact it seems that NO message posted from outside Birmingham is
getting through the link, so, until the problem is fixed I'll have to
repost them all..... sigh.

Steve's message follows. I'll do the same with Jonathan Cunningham's
followup later.

Aaron
=======================================================================

Date: Wed, 22 Mar 2000 11:04:27 +0000
To: Andrew E Sayers <ug55aes@cs.bham.ac.uk>
From: "Stephen F. K. Leach" <steve@watchfield.com>
Subject: Re: Running Pop-11

Hi Andrew,

>That said, I'd like to get rid completely of the need for load-time shell
>scripts - they cause problems for people who don't have/don't use the
>shell a script is written for, and we have a perfectly good language to do
>all this stuff with anyway :)

Yes!  Nothing would give me greater pleasure than getting rid of the
blasted setup scripts.  They have been one of the biggest drawbacks to
using Poplog throughout my 15 years of enjoyable programming with it.


>To that end, is there anything other than environment variables that is
>currently set-up by scripts?

No, but don't forget $PATH is changed.

In my opinion, the standard Poplog install on Linux should be changed
to use a more familiar layout.  Personally, I am in favour of the
user-definable-layout approach that Apache uses.

For example, I would imagine that the default layout would install
Poplog into
     /usr/local/lib/poplog
and add the binaries to
     /usr/local/bin
And that during installation, the binaries would be compiled with the
location of the libraries.  This knowledge would eliminate the need for
a separate setup.

I have actually gone quite a long way down this path already.  The
setup I posted in reply to Terry Dartnall was adapted from my setup.
What I have is a bunch of C programs that I compile and stuff the
executables in
   /usr/local/bin
These C programs are responsible for dispatching Poplog appropriately.

Most importantly, one of these programs is responsible for dispatching
Poplog for CGI scripting.  Another I use for writing scripts that
begin
     #!/usr/local/bin/poplog
     ...
which is really useful for simple scripts.

I am happy to repost all this stuff.  However, I am aiming to put it
all on http://www.poplog.org/ within the next fortnight.


><snip - environment variables>
>
>Thanks - my next question was going to be about the minimal set needed :)

There is no official minimal set.  This is what I use with
no problem however.
   usepop, popcom, popsrc, popsys, popexternlib, popobjlib, popautolib,
   popdatalib, popliblib, poppwmlib, popsunlib, popvedlib, poplocal,
   poplocalauto, poplocalbin, popcontrib, popsavelib, popcomppath,
   popsavepath, popexlinkbase
Note that poppwmlib, popsunlib can be omitted safely under Linux.

It is also worth remarking that ALL of these can be given good defaults
derived from $usepop.

Steve