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 Ra
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://do
Hi Claes, Thanks for the effort in splitting the package.
Would any users of the graph library object to dropping support for 5.x?
On Tue, Dec 11, 2018 at 10:19 PM Claes Wallin (韋嘉誠)
wrote:
>
> I am trying to split the package graph into graph-doc and graph-lib,
> see: https://github.com/stchang/
I am trying to split the package graph into graph-doc and graph-lib,
see: https://github.com/stchang/graph/pull/37
So far, the package has been compatible with Racket 5.3.2, and I image
the original author Mr. Chang would like to keep it that way, if
possible.
In their respective graph/info.rkt (
4 matches
Mail list logo
