On Tue, Jul 8, 2014 at 8:14 AM, Matthew Flatt mfl...@cs.utah.edu wrote:
At Tue, 08 Jul 2014 14:08:27 +0200, Jan Dvořák wrote:
Can you provide some guidelines on docs naming?
I am responsible for half of the conflicts. :-)
A package X that provides a collection X of the same name should
At a high-level, I think conflicts should be resolved by persuasion,
by long-suffering, by gentleness and meekness, and by love unfeigned.
We have had very few conflicts so far, but when they happen, I (the
package catalog maintainer) email the two package authors and let them
know what happened.
Yes, `raco setup` with no arguments would succeeded and should fix
things up at this point.
When you use `raco pkg update`, it effectively passes the `--tidy` flag
to `raco setup`. That is, `raco setup --tidy rackjure` would avoid the
problem, and it should also fix things up at this point.
It's
Ah, great. I didn't know about --tidy. Thank you.
I just pushed this change:
https://github.com/greghendershott/rackjure/commit/a70fa27662fd10c3c458f9dce77dff7bc73ef6fc
That should clear the rightmost column for all my packages (rackjure,
and projects using it).
On Thu, Jul 10, 2014 at 3:28
So I just renamed rackjure's manual.scrbl to rackjure.scrbl.
On the next raco setup I get:
raco setup: --- building documentation ---
raco setup: WARNING: duplicate tag: (def ((lib rackjure/alist.rkt) alist))
raco setup: in: unknown
raco setup: in:
On Wed, Jul 9, 2014 at 8:21 PM, Greg Hendershott
greghendersh...@gmail.com wrote:
On the next raco setup I get:
raco setup: --- building documentation ---
raco setup: WARNING: duplicate tag: (def ((lib rackjure/alist.rkt) alist))
raco setup: in: unknown
raco setup: in:
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:
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 several
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.
On Tue, Jul 8, 2014 at 8:14 AM, Matthew Flatt mfl...@cs.utah.edu 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
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 Developers
On Tue, Jul 8, 2014 at 11:35 AM, Matthew Flatt mfl...@cs.utah.edu 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
At Tue, 8 Jul 2014 11:49:49 -0400, Sam Tobin-Hochstadt wrote:
On Tue, Jul 8, 2014 at 11:35 AM, Matthew Flatt mfl...@cs.utah.edu 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
13 matches
Mail list logo
