[[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Nothing in the test suite of GNU Parallel currently depends on Vagrant > newer than 2023-08-10, and I will have no problem committing to only > depending on features that are before 2023-08-10 or 4 years old. > Since there are no licensing issues using 2.3.7, I will continue to use that. Thanks. With that policy, GNU Parallel has no actual problem in its code. Would you please state that decision explicitly in GNU Parallel, perhaps in the README or wherever people building it will see it? However, running the tests for Parallel will lead people to install Vagrant to make them work. So we should proactively help and encourage them to install version 2.3.7 rather than the latest version. Is there a place that distributes Vagrant 2.3.7's tar ball without requiring the user to run Javascript code? You could link to that. Otherwise, how about if you redistribute Vagrant 2.3.7's tar ball? These are much less work than making a fork. And no new name is needed. > AFAICT it should be possible to make a fork of 2.3.7 that simply > contains every commit before 2023-08-10 or 4 years old. That could be a good thing to do, Even better if the people working on it also fix the more important bugs, using new fixes that are not copied from later Vagrant versions. But I don't know where to look for people to do that job. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)
