On Thursday, April 30, 2020 at 3:59:49 PM UTC+8, Laurent wrote:
>
> Alex, that looks like an interesting workflow. Maybe worth a blog post? ;)
>
Well, it took longer than I anticipated, but here it is:
https://alex-hhh.github.io/2020/05/dependency-management-in-racket-applications.html
I
Sage Gerard writes:
> As long as I don't have to keep reorganizing my code to accommodate
> the tooling, then it's a night and day improvement. Would you mind
> terribly if I worked with you? I was mulling over this myself in the
> dev list, but I am happy to aid any existing effort.
I'd
As long as I don't have to keep reorganizing my code to accommodate the
tooling, then it's a night and day improvement. Would you mind terribly if I
worked with you? I was mulling over this myself in the dev list, but I am happy
to aid any existing effort.
Original Message
On
Sam Tobin-Hochstadt writes:
> This is very cool! One question -- for "main-distribution" packages,
> are you snapshotting the most-recent release catalog? Or
> pkgs.racket-lang.org? The latter is simpler, but the former is
> probably needed to make the examples in the README work. Otherwise,
>
This is very cool! One question -- for "main-distribution" packages,
are you snapshotting the most-recent release catalog? Or
pkgs.racket-lang.org? The latter is simpler, but the former is
probably needed to make the examples in the README work. Otherwise,
if, say, "typed-racket-lib" on May 1
Alex Harsanyi writes:
> As an application writer, I am on the other side of this problem, by
> depending on other packages. Having limited time to work on my project I
> want to upgrade package dependencies at my own pace.
I'm in a similar position since I operate a few Racket applications.
Alex, that looks like an interesting workflow. Maybe worth a blog post? ;)
On Thu, Apr 30, 2020 at 12:11 AM Alex Harsanyi
wrote:
>
> You could both send packages to the package catalog and instruct your
> users to use a different package source if they wish to use old versions.
> I don't see
You could both send packages to the package catalog and instruct your users
to use a different package source if they wish to use old versions. I
don't see these two options in conflict with each other.
As an application writer, I am on the other side of this problem, by
depending on other
8 matches
Mail list logo
