Right, that's a good option. For the moment, it wouldn't even need a branch, just point at the current version of the package while the 6.x-compatible version moves on. It's a mature package, and if people need any new functionality that gets implemented later, they should be prepared to upgrade Racket. If there emerges a pressing need for upgrading the 5.x-compatible version, say for some security update, that could be handled at that time.
They aren't that many versions. Thanks for the tip! -- /c On Thu, Dec 13, 2018 at 7:42 AM Ben Greenman <benjaminlgreen...@gmail.com> wrote: > > Another option > > - make a branch for the Racket 5 code > - add version exceptions [1] to pkgs.racket-lang.org > - split the repo on the master branch > > The downside to this plan is that someone needs to add a version > exception for every 5.x version of Racket that `graph` wants to > support. > > [1] > http://docs.racket-lang.org/pkg/getting-started.html#%28part._.Version_.Exceptions%29 > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
