On Wed, Dec 12, 2012 at 4:01 PM, Ryan Culpepper r...@cs.utah.edu wrote:
On 12/12/2012 03:58 PM, Jay McCarthy wrote:
I agree with Carl.
But I would make an even stronger suggestion, I would suggest that you
completely drop support for old Racket versions and if necessary
release webapis-lts
On Wed, Dec 12, 2012 at 8:55 PM, Asumu Takikawa as...@ccs.neu.edu wrote:
On 2012-12-12 14:29:32 -0500, Ryan Culpepper wrote:
I'm trying to understand how things are supposed to work in planet2
without version information.
Maybe this was discussed in the other (quite long) thread about Planet
On Wed, Dec 12, 2012 at 11:48 PM, David Vanderson
david.vander...@gmail.com wrote:
I was professionally writing Ruby code as that community struggled through
package issues. I hope that experience can shed some light here. Also I'd
like to understand the basic use cases and how they work in
At Thu, 13 Dec 2012 08:17:32 -0700, Jay McCarthy wrote:
As an aside in response to this whole thread, [...]
I recommend that further complaints and suggestions take the form of a
patch.
Creating a patch is more difficult, more time consuming, and you have
to understand even more details of
On 2012-12-13 08:17:32 -0700, Jay McCarthy wrote:
Why aren't you just only using the development version?
This mainly comes up if I want to test the uploaded version to make sure
it works. I can probably figure out a better workflow though (such as
keeping around a release version of Racket to
I'm trying to understand how things are supposed to work in planet2
without version information.
Let's say I release a package, webapis. Time passes, and I notice that
Racket gets some cool new features (eg, better SSL support) that the
webapis package should use. I write the code, and ...
I believe it is by design that Planet 2 does not resolve this kind of
issue. This gives us room to experiment with different solutions without
committing to one up-front, since Planet 1 ran into various limitations of
its built-in policies.
I will propose one possible solution for your webapis
I agree with Carl.
But I would make an even stronger suggestion, I would suggest that you
completely drop support for old Racket versions and if necessary
release webapis-lts and scriblogify-lts packages that conflict
with webapis and can only work on old versions. The LTS ones
wouldn't be
On 12/12/2012 03:13 PM, Carl Eastlund wrote:
I believe it is by design that Planet 2 does not resolve this kind of
issue. This gives us room to experiment with different solutions
without committing to one up-front, since Planet 1 ran into various
limitations of its built-in policies.
I will
On Dec 12, 2012 3:14 PM, Carl Eastlund c...@ccs.neu.edu wrote:
I will propose one possible solution for your webapis example.
Distribute a primary wrapper package called webapis and separate specific
versions such as webapis1, webapis2, and so forth. Have the code in
webapis determine at
On 12/12/2012 03:58 PM, Jay McCarthy wrote:
I agree with Carl.
But I would make an even stronger suggestion, I would suggest that you
completely drop support for old Racket versions and if necessary
release webapis-lts and scriblogify-lts packages that conflict
with webapis and can only work on
On 2012-12-12 14:29:32 -0500, Ryan Culpepper wrote:
I'm trying to understand how things are supposed to work in planet2
without version information.
Maybe this was discussed in the other (quite long) thread about Planet
2, but another thing that the lack of versions makes difficult is having
I was professionally writing Ruby code as that community struggled
through package issues. I hope that experience can shed some light
here. Also I'd like to understand the basic use cases and how they work
in planet2.
As a user, here are my 2 use cases:
1. My friend tells me about awesome
13 matches
Mail list logo
