Hi Frank! > Le 22 déc. 2018 à 21:12, Frank Heckenbach <f.heckenb...@fh-soft.de> a écrit : > > Sorry, now I seem to be the one to have trouble using your patch: > > - I guess the right thing is to clone the repository,
Yes, it is. > but > unfortunately git is quite data hungry and I'm a bit short on data > volume (no broadband in my new appartment yet, and mobile data is > paid in gold here in Germany), Ouch. We're lucky in France, that's very cheap. > so I could only do it on a server > on which I have access (in the hope of running "make dist" or so > to get it to my machine then), but after downloading >100 MB (like > I feared), bootstrap failed with lots of warnings and errors (the > server is still running jessie, which I can't change, guess that's > too old to bootstrap bison). I don't think so, but I don't actually know. > I suppose I could ask you to send me a "dist" archive for testing > now, or if only "data" files need changes compared to 3.2.2, post > those, but for testing future changes, that's not a very nice > workflow. Is there any better way? Please find the tarball here: https://www.lrde.epita.fr/~akim/private/bison/bison-3.2.1.127-777b.tar.gz https://www.lrde.epita.fr/~akim/private/bison/bison-3.2.1.127-777b.tar.xz The best way would be to provide tarballs directly from my GitHub repo. After all, it's already running travis for the tests, it can easily build tarballs. However, I don't know how to expose them, I don't think there is a free (as in beer) way to do that. If you have an idea, I'll take it!
