On 3/9/08, Harald Geyer <harald at lefant.net> wrote:
> I guess anybody with CVS write access could update the website,
> but I'm not familiar with the details.
Harald, if you want to edit relatedprojects.shtml, please go right ahead.
Shell access is a separate permission apart from CVS permission --
shell access is enabled for you. An administrator can enable it for
any developer.
The web pages are in CVS, in maxima/htdocs/ (sibling directory
to maxima/maxima which contains src, share, etc).
The web pages are named .shtml, because they have server-side
includes, I guess.
There is a Maxima home directory at SF:
/home/groups/m/ma/maxima/, and pages appearing
in /home/groups/m/ma/maxima/htdocs/ are served by the SF
web server. If you login via ssh,
e.g. ssh robert_dodier at maxima.sourceforge.net
you should be able to cd to the Maxima home directory.
Usually what I do is edit the web pages in a sandbox on my
desktop box, commit them to CVS, then login via ssh and
run cvs update in /home/groups/m/ma/maxima/htdocs/.
PLEASE NOTE that you should specify which files to update
i.e. "cvs update foo.shtml" instead of "cvs update"; if I recall
correctly, there are some very large, strange files in CVS
that need not and should not be updated.
I suppose someone, maybe me, should cvs rm them.
I've tried to set umask and chmod and chgrp stuff so that
cvs update can overwrite files in htdocs if run by other
developers. Anyone working in htdocs should do likewise.
Some of the files in htdocs on the shell server are out of date
with respect to CVS. Someone ought to synchronize that
stuff with CVS, either by committing or abandoning the changes.
I guess someone, maybe me, ought to write this stuff down,
probably in maxima/maxima/README.developers-howto.
Hope this helps,
Robert Dodier