[racket-dev] A grab-bag of issues

Yesterday, Matthew Flatt wrote:
> At Thu, 4 Jul 2013 12:52:10 -0400, Sam Tobin-Hochstadt wrote:
> 
> > 2. It's possible to get lots of undefined tags in the documentation
> > builds.  Should this be remedied with more build dependencies, or
> > will it be fixed with the online documentation server, or
> > something else?
> 
> Mostly through an online documentation server and declaring certain
> documentation links to be "indirect" (which may sometimes involve
> adjusting the documentation content).

If the documentation requires consulting a server, then why distribute
them in the first place?  There were a whole bunch of issues (most
notably a lack of a full text search) that are much easier to deal
with if the documentations are all on-line.


> > 5. GitHub recently introduced "Releases", which allow you to serve
> > arbitrary downloads. This might be useful for the "plt/libs"
> > repository.  More info here:
> > https://github.com/blog/1547-release-your-software . Even without
> > this, we might want to switch to downloading native packages as
> > zip files instead of requiring git to build from source.
> 
> I imagined that we would having a catalog server for the
> native-library packages, but it's good to know about support for
> Releases from GitHub, and I'll look into that more.

AFAICT, there is not much in this, and you get releases by just
pushing tags -- so they're already there:

    https://github.com/plt/libs/releases

(Also, serving individual files is fine from our git server.)

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!