Re: [racket-dev] Packages

2013-04-08 Thread Neil Toronto
I probably shouldn't jump into this because I've barely used the new package system, but here I go... On 04/08/2013 03:17 PM, Eli Barzilay wrote: 50 minutes ago, Jay McCarthy wrote: I don't see how you can start from this place and say, "I am making the elis-awesome-stuff package, so therefore

Re: [racket-dev] Packages

2013-04-08 Thread Eli Barzilay
50 minutes ago, Jay McCarthy wrote: > On Mon, Apr 8, 2013 at 2:18 PM, Eli Barzilay wrote: > > It all starts at how someone is expected to approach developing a > > "package", regardless of how this is defined in the current > > system. A quick way to get to the core of the problem is to > > consi

Re: [racket-dev] Packages

2013-04-08 Thread Jay McCarthy
On Mon, Apr 8, 2013 at 2:18 PM, Eli Barzilay wrote: > This is a (long) criticism of the current state of the package system. > (It is a by-product of PR13669, where I raised that point.) > > Executive summary: I very strongly think that "pkg create" should > change. See the bottom for my suggesti

Re: [racket-dev] Packages

2013-04-08 Thread Matthias Felleisen
Matthew wouldn't ask for a patch if he wanted you to go thru the work and would reject the patch out of hand. If, however, the patch is "delete design completely, use this one instead", he and the rest of dev may reject it too. In between all shades of grey. -- Matthias On Apr 8, 2013, at

Re: [racket-dev] Packages

2013-04-08 Thread Eli Barzilay
A few minutes ago, Matthew Flatt wrote: > I stand by my recommendation from December: > > http://lists.racket-lang.org/dev/archive/2012-December/011218.html > > That is, I think this suggestion should be phrased as a patch. > > As implied in my quote below, I tried something much like you're >

Re: [racket-dev] Packages

2013-04-08 Thread Matthew Flatt
I stand by my recommendation from December: http://lists.racket-lang.org/dev/archive/2012-December/011218.html That is, I think this suggestion should be phrased as a patch. As implied in my quote below, I tried something much like you're describing, and I was unhappy with the resulting compli

[racket-dev] Packages

2013-04-08 Thread Eli Barzilay
This is a (long) criticism of the current state of the package system. (It is a by-product of PR13669, where I raised that point.) Executive summary: I very strongly think that "pkg create" should change. See the bottom for my suggestion. * Most code development happens in a single collection