Hi Waldek,
I wrote:
> > I've just realised that we may need multiple versions of corepop for
> > bootstrapping a new poplog on different machines.
You responded:
> One version (per platform) should be enough. However, preparing
> such version needs some care: ATM there are two "major" versions of
> ncurses library. Change in major version is deemed incompatible
> change, so we have binary incompatiblity. In 'poplog_base'
> tarball I include 'corepop' linked without ncurses, so it only
> uses compatible libraries. Another things is to build corepop
> on oldest supported system: linking on new system tends to
> introduce dependence on newer library.
One simple change would be to provide old and recent versions of corepop in the
distribution package, marked with extra suffixes, and to change the poplog
installation process so that instead of replacing corepop with a new version
every time poplog is rebuilt, it leaves the old version(s) of corepop unchanged
and uses a copy of one of them for the installation process.
Users who wish to re-link, e.g. after installing an extension or bugfix, will
then have the option to re-link using the most recently built version of corepop
or to go back to an older version provided when poplog was originally
downloaded, which is not available now after re-linking, unless users save their
first version of corepop before installing.
I am aware that some, but not all, of the documentation in the sysdoc directory
http://www.cs.bham.ac.uk/research/projects/poplog/sysdoc
is now out of date.
Documentation for a system as complex as poplog needs a lot of teamwork.
Aaron
http://www.cs.bham.ac.uk/~axs
