On Thu, 30 May 2002, Frank Heckenbach wrote:
Ernst-Ludwig Bohnen wrote:
I had been out several weeks, so the answer is somewhat late. I still like to contribute, though missing or poor documentation may be a severe handicap. But nevertheless let's start with an account with ssh, scp, wget etc. and some (writable) disk space.
OK. Details by private mail.
BTW, in order to compile and test some units with the new gpc-2.1 release I realised that my lovely GPC installer (install.gpc) doesn't work anymore. Beside some simple other problems (wich have been solved within the script) after unzipping the gpc-2.1.tar.gz file the dir name is gpc-20020510 instead of gpc-2.1 but install.gpc expects only identical base names. I could repair this behavior as well in the script, but we would loose the very usefull feature of simple switching between different gpc versions in case of trouble.
Some who worked on this script may already have solved (part of) this problem, but I didn't follow this closely ...
Two questions:
- Is there a way to access ALL gpc versions from the same URL-directory, possibly by symlinks?
- Could gpc-versionxyz.tar.gz resolve after untaring to dir gpc-versionxyz ?
If I am not wrong a link ../beta/gpc-20020510.tar.gz to ../current/gpc-2.1.tar.gz can do the job in a single step,
... except that it isn't really a beta version. ;-)
You are right, it is not a very clean solution.
and in addition dissolve the (little) confusion that the newest GPC-manual for 2.1 is labeled with 'version 20020510' anyway.
As far as I'm concerned, I don't give much for the "release" version numbers, anyway. I'd prefer to always use the date. But somehow the release versions seem to be "expected" ...
Anyway, the next updates will be labelled alpha again (though they probably won't be less stable than 2.1, but I'll do less thorough testing before uploads). I think we should leave 2.1 (and only this one) in current, shouldn't we? OTOH, we can probably remove the betas before 2.1 soon (whereas it will probably be some time before any 2.2 betas will appear).
So maybe I should link 2.1 to 20020510 in current, and the script would need to find the latest in alpha, beta and current (maybe with an option to ignore alphas for those who don't want to try them) ...?
Ok, I change the script this way: looking in current by default and as an option looking in alpha and/or beta (but expecting always the date format gpc-yyyymmdd.tar.gz, which resolves to dir gpc-yyyymmdd). I put the last version to ../contrib/ernst/tools/install.gpc. It allows selection of URLs & versions at the command line, but 'beta' is the default yet.
Thank you for help. Ernst-Ludwig
Frank
-- Frank Heckenbach, frank@g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html