> ug55aes@cs.bham.ac.uk wrote:
>
> > Most of the scripts (notably the main 'poplog' script) were written in
> > csh, if I remember.
>
> Do you mean $usepop/pop/com/poplog? There is an alternative
> $usepop/pop/com/poplog.sh supplied, at least for linux and sun, that
> works with Bourne type shells like sh, bash and ash.
I'd forgotten that. I'll change the install script to link to that
instead.
Still, I think that INSTALL_LIKE_BHAM and INSTALL_(NO)MOTIF use csh.
> > I thought about it, but in the unlikely event that someone has a weird
> > set-up with different .so.6 and .so files, poplog would still be happy.
>
> Not clear. What if the .so file were linked to some older or newer
> version like .so.4 or .so.8? This is just the sort of situation where
> people would be left wondering what was going on.
>
> > Besides that, I don't know an easy way of getting a bash script to check
> > the destination of a symlink :)
>
> ls -l <link> | grep <destination> ?
>
Good idea. I'll make that change too, then.
> > popcd.tar is a tarball of gzipped tarballs, containing everything you need
>
> Well maybe you should offer it as an optional extra, since it is so
> big. You don't actually need it to run, or even rebuild, poplog. I'm
> sure there is some splendid stuff in it, but maybe some duplication as
> well, and if the point of this script is to get people started, you
> might scare them off unnecessarily with 90 minute downloads.
What do you need, then - just linux1553, or are there any others?
- Andrew
|