It would be great if we could move everything to github - even a plain copy in its current state - as the git tools would make collaboration much easier.
I originally made the https://github.com/poplog "organisation" account, but I did it under such an old email address that I simply don't have access to it any more (even github has killed that user). But we/I can make another (and maybe reclaim the old when we have some traction). So, to begin with, we have to tackle one of the 2 hardest things in computing: what name to give it? :-) Perhaps openpoplog (though it always was)? Any other suggestions? When we have the repo we can discuss what should go in it... Cheers, Ian On Fri, 7 Feb 2020 at 09:01, Aaron Sloman <[email protected]> wrote: > Hi Nick, > > > It's my understanding that Waldek has a repo, with significant commits > for > > 64-bit and Arm support. I'm unsure what has been tested and on what > > platforms / hardware. > > https://github.com/hebisch/poplog/commits/master > > > > with README.md: > > "This is cleaned up version of Poplog sources, currently only core part." > > I take it you haven't been on this list during the last couple of months. > There is now Poplog version 16 located here: > > https://www.cs.bham.ac.uk/research/projects/poplog/V16/AREADME.html > > It starts: > > STILL UNDER CONSTRUCTION > > Linux Poplog Version 16 is ready for testing: > After required linux libraries have been installed[*], > a single script fetches and installs Poplog V16[*] > > After running that script there's an optional extra command to relink with > motif. > > It that file, and others there should answer your questions, at least as > regards ubuntu, debian, arch, and Redhat based versions of linux (fedora, > CentOS, Scientific linux). > > The getpoplog.sh script can be run with or without -nopie, as explained in > the file. That default will probably be reversed as newer versions of linux > seem to need the -nopie version (pie = position independent execution). > > Please report your experiences to the list. I am struggling a bit to keep > up at present because other pressures. That may be true of other, more > expert, participants also. > > Eventually I expect it all to go onto github, but there are still some > questions about what should and should not be in it and a small 'startup' > bug that so far only affects programs that are run as > > pop11 command.... > > where command makes use of itemread/readitem and its derivatives, which can > always, for now be replaced by > > pop11 > : command ... > > The install instructions have been tested by several people on this list -- > I don't know how many. There are people working on reviving old packages, > e.g. the vision and neural packages. > > The AREADME.html file has grown too large and repetitive and I plan to fix > that. > > I hope that when everything is working perfectly (!) and there's a > consensus about what should be included by default and what should not, > then all the former can be installed on github, and perhaps also the > optional extras after some testing. > > Anything you can do to check out the current version will be appreciated. > > Waldek, > > Would it be possible to add something like the above answer to the github > web site so that, for the time being people can be redirected to the > V16/AREADME.html for information on installing and using Poplog with all > the old subsystems and packages? > > Aaron > >
