Thanks to Jonathan for asking me to go and have a look at this thread!
In message <bnr5am$3167$1@soapbox.cs.bham.ac.uk>,
cherry@sdf.lonestar.org writes
>On Thu, 30 Oct 2003, Aaron Sloman wrote:
>
>> Date: Thu, 30 Oct 2003 11:55:10 +0000 (UTC)
>> From: Aaron Sloman <A.Sloman@cs.bham.ac.uk>
>> To: pop-forum@cs.bham.ac.uk
>> Subject: Re: New poplog with bug in Pop-11/Poplog back-end compiler fixed
>> (PS)
>>
>> Correction to new system, alas.
>>
>> I wrote, last night:
[...]
>> Anyhow, I have now rebuilt the tar file with the fixes. If anyone has
>> already downloaded it since my previous posting, but does not wish to
>> get all 21 Mbytes again, then
>[...]
>
>Is the CVS repository functional ? The
>http://www.poplog.org/scripts/cvsweb/packages link doesn't seem to work.
>
>
>Once again, I want to point out that such a large piece of sofware as
>poplog should be under CVS. If nobody has the time for that, I'd like to
>help out. Pls point out the resource (ie; cvs server) or tell me if its ok
>to start a repository on sourceforge.
>
Try browsing http://openpoplog.sourceforge.net. If this page doesn't let
you get anywhere, then try http://sourceforge.net/projects/openpoplog
directly. The popup menus at the former don't appear under some browser
versions, e.g. older Netscape browsers.
The Windows version of Poplog 15.53 is there under CVS, along with parts
of other versions.
It has been pointed out to me that the "nightly CVS tarball" link is/was
broken. For a while, SourceForge stopped generating the automatic
repository tarballs, but you can still access the repository via a CVS
client.
The CVS uses a version of the standard Poplog directory tree, where
platform-specific files are kept in the usual directories with a
platform suffix added to indicate CPU, OS and, optionally, window
manager. E.g. openpoplog/poplog/pop/src_x86_Linux_Motif.
>Aaron, I'm sure you'd be able to appreciate the decentralized nature of
>development, once the CVS way has been run in. P'haps we'd even be able to
>write a front end to CVS for ved, just like emacs pcl-cvs. ( I'm not
>certain it exists now ... )
>
All volunteers are appreciated. If you'd like to get involved, there are
a number of jobs to do.
Top of the list are:
1. Load the code for the remaining versions into the existing CVS
structure. (Either Roger or I need to ask SourceForge for some
additional disk space).
2. Add the code for building an installation pack for the Windows
version.
3. Create a release for each platform.
4. Synchronise with changes made at Birmingham.
5. Tidy the CVS to correct a few mistakes made in the original load,
e.g. the pop directory should only contain platform-independent files.
6. Produce a new "all platforms" CD for Poplog, with an ISO image that
can be downloaded, file-by-file, using something like the Debian jigdo
tool.
7. Improve the PR site at openpolog.sourceforge.net.
8. Ask Graham and/or Steve (poplog.org) to link to the SourceForge
ViewCVS pages, once the remaining platforms are uploaded.
9. Arrange a (Christmas) shindig for the remaining Poplog volunteers to
consume much food and drink while debating a road-map for Poplog.
You could argue about the order, but assistance would be more useful.
If you need administrative support, contact either Roger or myself, via
the contact address on SourceForge.
I shall be picking up the baton again, for a few weeks, in a little
while, as soon as my ISP has ironed out the bugs in my ADSL service that
was supposed to go live yesterday.
>Best,
>
>Cherry.
>
>--
>cherry@sdf.lonestar.org
>Homepage - http://cherry.freeshell.org
>
>
>
>
Regards,
--
Jeff
(You can reply by posting back to c.l.p or, privately, via SourceForge email).
|