Brent,
I don't know whether I ever replied to this properly:
Date: Tue, 13 Apr 2004
From: Brent Fulgham
> Is any interesting work going on there? I'd like to
> take the source tree they were working on and use it
> as
> the basis of a clean Debian installer that would
> automate many of the setup tasks and make it simple
> to install Poplog.
John Duncan (somewhere in Australia) was working on this last July, but
I don't know what the end product was and whether he ever made it
generally accessible.
Since then I have simplified the installation process for PC+linux
poplog and I don't know if those changes need to be propagated to his
package.
The best place to start from scratch for a debian+pc (intel/amd) version
of poplog would be one of the packages for linux poplog, which include
all the sources required.
There are three packages at present -- I think are described in
http://www.cs.bham.ac.uk/research/poplog/freepoplog.html
though that file is now too long!
1. The core package linux-pc-1553.tar.gz (actually a symbolic
link as explained below). This changes least often.
about 10Mb
2. A slightly larger package (about 12.9Mb) which includes the above,
along with 'core' Birmingham extensions which go into
sub-directories of $poplocal/local, providing
auto/, com/, help/, lib/, teach/, setup/, rclib/, rcmenu/,
Some of these should go into $usepop/pop/lib/ instead
when I have time.
3. The full bham-linux-poplog.tar.gz which includes the other two
and a lot of other 'add-on' libraries (e.g. simagent toolkit,
popvision) and the new easy install scripts.
(It is possible to get from an installation of 2 to an installation
of 3 by using the popextras.tar.gz package, but I don't advertise
that much! I have put most effort into making 3 usable because most of
the people I know about who need poplog need that version, originally
created for our students to install on their home machines.)
So, in more detail:
1. http://www.cs.bham.ac.uk/research/poplog/new/linux-pc-1553.tar.gz
That is actually a symbolic link to the latest version, in the
same directory, currently
10059834 Apr 17 16:39 linux-pc-1553e.tar.gz
That includes the 'core' linux pc package, which has all the system
sources and stuff to link and setup. It may include minor bugfixes
either in the core sources, in Ved, in X stuff, in install scripts.
It rarely changes, apart from install stuff and documentation.
(I have got careless about producing a list of change-notes. I must
start being more thorough, though time-pressure is very great.)
2. http://www.cs.bham.ac.uk/research/poplog/new/linux-poplog.tar.gz
(About 12.9 Mbytes)
That includes package 1 for 'core' linux poplog with some 'core' bham
extensions (in bham.tar.gz) installation scripts, sample test scripts,
and instructions.
3. http://www.cs.bham.ac.uk/research/poplog/bham-linux-poplog.tar.gz
(About 21 Mbytes)
That includes package 2 (and therefore 1), plus various add on libraries
and easy install scripts, etc. it always includes the full sources for
the most recent version of pc+linux poplog in the contents of package 1.
When I get a week or so clear (maybe less is needed) I'd like to abolish
the distinction between the frst two packages by moving much of what
is in the bham.tar.gz file, which now goes into $poplocal/local,
so that it goes into the main tree under $usepop/pop. Then package
1 will be enlarged and package 2 will disappear. Maybe some leftovers
from it (e.g. support for latex and news in Ved) would go only into
package 3.
Then rclib, rcmenu, would go into $usepop/pop/lib/, and their startup
files rclib.p rcmenu.p would go into $usepop/pop/lib/lib so that they
can be found by 'uses' (now such bham files for 'uses' go into
$poplocal/local/lib )
Various other things rationalising Ved, improving readline, making
prwarning give filename and line numbers, extending 'matches' to work
with lvars, etc. etc. would go into the main auto/ lib/ help/ and teach/
directories.
It will take me much longer to produce or correct ref/ documentation
(partly because I don't like working with the 'fancy' Ved characters.
Now that I know what you are doing, if you start from a snapshot of the
linux+pc sources in package 1 I could start carefully producing a series
of tar-balls that can be un-tarred over $usepop to install upgrades.
If someone then wished to put all that onto sourceforge that would be
fine with me -- I won't have time in the foreseeable future.
Any package you produce could be installed here
http://www.cs.bham.ac.uk/research/poplog/debian/
(currently an empty directory)
Does that make sense?
Where have you got to now, and have you looked at John Duncan's
poplog for debian?
Aaron
|