"Loris Bennett" <loris.bennett-j/[email protected]> writes: > "Loris Bennett" > <loris.bennett-j/[email protected]> > writes: >> Hi, >> >> I am trying to write >> >> rMATS-turbo-4.3.0-gfbf-2024a.eb >> >> For this I need to create >> >> STAR-2.7.11b-GCC-13.3.0.eb >> >> which in turn depends on >> >> xxd-<?>-GCCcore-13.3.0.eb >> >> where '<?>' is some version of Vim, xxd apparently being some component >> of Vim. >> >> The Vim people seem to have a somewhat promiscuous (at least to this >> prudish Emacs user) release policy - the GitHub page claims no actual >> releases but 18,000 tags >> >> https://github.com/vim/vim/releases >> >> often several per day. >> >> For want of any other criteria, I would probably just chose the most >> recent, but maybe that is not the best option. >> >> Does anyone (a bohemian Vim user maybe) have any advice on this? > > If I compare the latest version with that used in for > xxd-9.1.0307-GCCcore-13.2.0.eb, via the mechanism on GitHub I get > > Comparing changes > Choose two branches to see what’s changed or to start a new pull request. > If you need to, you can also > or learn more about diff comparisons. > ... > There isn’t anything to compare. > > v9.1.1267 is up to date with all commits from v9.1.0307. Try switching the > base for your comparison. > > So I guess the latest version is fine (as are many others ...).
Ah. Comparing A with B is not the same as comparing B with A. If I switch base as suggested, then I do see a few differences: Comparing changes Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons. ... 59 contributors Commits 4,573 Files changed 4,284 So I still don't have any particular criterion for choosing any version other than the latest. -- Dr. Loris Bennett (Herr/Mr) FUB-IT, Freie Universität Berlin
