[racket-dev] Release for v6.1 has begun

2014-07-08 Thread Ryan Culpepper
The release process for v6.1 has begun: the `release' branch was created for any work that is left and is now bumped to v6.0.900.900. You can go on using the `master' branch as usual, it is now bumped to v6.1.0.1 (to avoid having two different trees with the same version). If you have any bug-fix

Re: [racket-dev] current packages' docs, errors, and conflicts

2014-07-08 Thread Matthew Flatt
At Tue, 8 Jul 2014 11:49:49 -0400, Sam Tobin-Hochstadt wrote: > On Tue, Jul 8, 2014 at 11:35 AM, Matthew Flatt wrote: > > At Tue, 8 Jul 2014 10:15:10 -0400, Sam Tobin-Hochstadt wrote: > >> - I think we need to support planet packages -- there are some people > >> still releasing new ones, and the

Re: [racket-dev] current packages' docs, errors, and conflicts

2014-07-08 Thread Sam Tobin-Hochstadt
On Tue, Jul 8, 2014 at 11:35 AM, Matthew Flatt wrote: > At Tue, 8 Jul 2014 10:15:10 -0400, Sam Tobin-Hochstadt wrote: >> - I wonder if using Docker instead of VirtualBox could make >> incrementality easier, since that's one of things that they focus on. > > I don't think it would be easier, but i

Re: [racket-dev] current packages' docs, errors, and conflicts

2014-07-08 Thread Matthew Flatt
At Tue, 8 Jul 2014 10:15:10 -0400, Sam Tobin-Hochstadt wrote: > - I wonder if using Docker instead of VirtualBox could make > incrementality easier, since that's one of things that they focus on. I don't think it would be easier, but it might be more efficient and even easier to set up, so it see

Re: [racket-dev] current packages' docs, errors, and conflicts

2014-07-08 Thread Matthew Flatt
At Tue, 8 Jul 2014 09:08:34 -0400, Sam Tobin-Hochstadt wrote: > On Tue, Jul 8, 2014 at 8:14 AM, Matthew Flatt wrote: > > At Tue, 08 Jul 2014 14:08:27 +0200, Jan Dvořák wrote: > >> On Tue, 2014-07-08 at 12:46 +0100, Matthew Flatt wrote: > >> > The rightmost column of the table may need some explana

Re: [racket-dev] current packages' docs, errors, and conflicts

2014-07-08 Thread Sam Tobin-Hochstadt
This is lovely. A few thoughts: - I wonder if using Docker instead of VirtualBox could make incrementality easier, since that's one of things that they focus on. - I wanted to be able to see which of my packages had problems, so I wrote this PR: https://github.com/plt/racket/pull/721 but I'm not

Re: [racket-dev] current packages' docs, errors, and conflicts

2014-07-08 Thread Jan Dvořák
On Tue, 2014-07-08 at 13:14 +0100, Matthew Flatt wrote: > A package "X" that provides a collection "X" of the same name should > probably also call its documentation "X". Thanks, I've fixed mine. Looking forward to having pkg-docs at a single place. :-) _ Racket Develope

Re: [racket-dev] current packages' docs, errors, and conflicts

2014-07-08 Thread Sam Tobin-Hochstadt
On Tue, Jul 8, 2014 at 8:14 AM, Matthew Flatt wrote: > At Tue, 08 Jul 2014 14:08:27 +0200, Jan Dvořák wrote: >> On Tue, 2014-07-08 at 12:46 +0100, Matthew Flatt wrote: >> > The rightmost column of the table may need some explanation. The column >> > highlights conflicts among names of package-inst

Re: [racket-dev] current packages' docs, errors, and conflicts

2014-07-08 Thread Matthew Flatt
At Tue, 08 Jul 2014 14:08:27 +0200, Jan Dvořák wrote: > On Tue, 2014-07-08 at 12:46 +0100, Matthew Flatt wrote: > > The rightmost column of the table may need some explanation. The column > > highlights conflicts among names of package-installed executables, > > foreign libraries, and documents. Cu

Re: [racket-dev] current packages' docs, errors, and conflicts

2014-07-08 Thread Jan Dvořák
On Tue, 2014-07-08 at 12:46 +0100, Matthew Flatt wrote: > The rightmost column of the table may need some explanation. The column > highlights conflicts among names of package-installed executables, > foreign libraries, and documents. Currently, all the conflicts are > document names, because sever

[racket-dev] current packages' docs, errors, and conflicts

2014-07-08 Thread Matthew Flatt
I've been working on a service that builds all packages listed at "pkgs.racket-lang.org". The idea is to run builds regularly (at least once a day) and link to documentation and build-status information from "pkgs.racket-lang.org". Here's a table showing the current results for each package: ht