Re: [racket-dev] Planet2 urls

2013-01-09 Thread Jay McCarthy
The URLs are pretty easy to change. The dispatch tables here: https://github.com/plt/racket/blob/master/collects/meta/planet2-index/basic/main.rkt#L35 and here: https://github.com/plt/racket/blob/master/collects/meta/planet2-index/official/main.rkt#L95 just need to change, and if the first does

[racket-dev] Planet2 urls

2013-01-09 Thread Eli Barzilay
6 hours ago, Sam Tobin-Hochstadt wrote: > On Wed, Jan 9, 2013 at 8:31 AM, wrote: > > + (format "https://pnr.racket-lang.org~a"; k-url) > > Can we name this something user-memorable? Ideas: packages.r-l, > package.r-l, pkg.r-l (goes with the `raco` command), ... +3 -- assuming tha

Re: [racket-dev] planet2 and versions

2012-12-13 Thread David Vanderson
On 12/13/2012 07:19 AM, Jay McCarthy wrote: This is on my future plans to make a "raco pkg bundle" that will produce a big tar ball that and can be installed on another machine and get the same packages (even if they are no longer available at their sources with those versions) installed. I just

Re: [racket-dev] planet2 and versions

2012-12-13 Thread Asumu Takikawa
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 t

Re: [racket-dev] planet2 and versions

2012-12-13 Thread Sam Tobin-Hochstadt
On Thu, Dec 13, 2012 at 10:08 AM, Jay McCarthy wrote: > >> Finally, as a meta-point, is there any evidence that just throwing away >> versions will work? Any precedents? So far, this seems like a classic case >> of throwing the baby out with the bathwater: versions sometimes cause >> problems... s

Re: [racket-dev] planet2 and versions

2012-12-13 Thread Matthew Flatt
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 Plan

Re: [racket-dev] planet2 and versions

2012-12-13 Thread Jay McCarthy
On Wed, Dec 12, 2012 at 11:48 PM, David Vanderson 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 planet2. > > As a user,

Re: [racket-dev] planet2 and versions

2012-12-13 Thread Jay McCarthy
On Wed, Dec 12, 2012 at 8:55 PM, Asumu Takikawa 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 > 2, but an

Re: [racket-dev] planet2 and versions

2012-12-13 Thread Jay McCarthy
On Wed, Dec 12, 2012 at 4:01 PM, Ryan Culpepper 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" an

Re: [racket-dev] planet2 and versions

2012-12-12 Thread David Vanderson
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 l

Re: [racket-dev] planet2 and versions

2012-12-12 Thread Asumu Takikawa
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 b

Re: [racket-dev] planet2 and versions

2012-12-12 Thread Ryan Culpepper
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 wo

Re: [racket-dev] planet2 and versions

2012-12-12 Thread Eli Barzilay
On Dec 12, 2012 3:14 PM, "Carl Eastlund" 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 compile-t

Re: [racket-dev] planet2 and versions

2012-12-12 Thread Ryan Culpepper
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 pr

Re: [racket-dev] planet2 and versions

2012-12-12 Thread Jay McCarthy
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 i

Re: [racket-dev] planet2 and versions

2012-12-12 Thread Carl Eastlund
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"

[racket-dev] planet2 and versions

2012-12-12 Thread Ryan Culpepper
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 ...

Re: [racket-dev] planet2

2012-12-10 Thread Neil Van Dyke
Jay McCarthy wrote at 12/10/2012 02:22 PM: On Sun, Dec 9, 2012 at 1:26 PM, Neil Van Dyke > wrote: * I'm very concerned about discarding support for mixing versions of packages. PLaneT 1 didn't fully nail this, but I suspect planet2 is punting needlessly

Re: [racket-dev] planet2

2012-12-10 Thread Jay McCarthy
On Sun, Dec 9, 2012 at 1:26 PM, Neil Van Dyke wrote: > My biggest comments on planet2... > > * I like the general ideas of permitting more decentralized sharing of > packages (such as through some kind of Git URLs). > > * I like the idea of making it easier to modify the source of a package > and

[racket-dev] planet2

2012-12-09 Thread Neil Van Dyke
My biggest comments on planet2... * I like the general ideas of permitting more decentralized sharing of packages (such as through some kind of Git URLs). * I like the idea of making it easier to modify the source of a package and share changes with upstream (which is needlessly cumbersome wi