Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When/how should we update Frog? #53

Closed
gasche opened this issue Feb 28, 2017 · 1 comment
Closed

When/how should we update Frog? #53

gasche opened this issue Feb 28, 2017 · 1 comment

Comments

@gasche
Copy link
Contributor

gasche commented Feb 28, 2017

greghendershott/frog#180 was just merged upstream, which fixes a bug that affects our blog (it makes it painful to read for (at least) Thunderbird users that subscribed to the RSS feed.) How can I make sure that the version of frog used to generate the blog contains the fix?

@bennn
Copy link
Member

bennn commented Feb 28, 2017

You can check by:

  • uninstalling frog on your machine (raco pkg remove frog)
  • re-installing frog (raco pkg install frog)
  • rebuilding the blog

If it looks good,* then it should look good on the website. Because building the website:

  • uses a travis script
  • which installs Racket v6.6
  • and then runs the website/blog's Makefiles;
  • the blog's Makefile runs raco pkg install frog
  • which gets the "most recent available frog"

Racket's basically "rolling release" for all packages. You can make a version exception (users of Racket v6.6 get the v6.6 of package "My-Pkg"), but frog isn't doing that so the website should be getting the most up-to-date.

(* If it doesn't look good, maybe wait a few hours for the Racket package server to update its copy of frog)

@bennn bennn closed this as completed Feb 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants