Re: [racket] the current package submission system is a mess

2014-11-12 Thread Ryan Davis
> > On Nov 5, 2014, at 17:53, Jay McCarthy wrote: > > Hi Ryan, > > > On Wed, Nov 5, 2014 at 7:14 PM, Ryan Davis wrote: >> The package submission system is hostile and incredibly frustrating to use. >> >> I've tried a bazillion times now to submit a package (check-sexp-equal) and >> ensure t

Re: [racket] the current package submission system is a mess

2014-11-06 Thread Jay McCarthy
On Wed, Nov 5, 2014 at 9:19 PM, wrote: > I also ran into trouble that it seemed like the correct url for a github > repo is not git: but github:, and it needed the branch name tacked on at the > end. This is not correct. If you refer to the package source documentation I linked before, there are

Re: [racket] the current package submission system is a mess

2014-11-06 Thread scott
I had similar issues (in particular with it being difficult to determine when my updates had been accepted by the server). I also ran into the "logging in" message which never made progress. That seemed to resolve by trying again the next day... I also ran into trouble that it seemed like the

Re: [racket] the current package submission system is a mess

2014-11-05 Thread Jay McCarthy
Hi Ryan, On Wed, Nov 5, 2014 at 7:14 PM, Ryan Davis wrote: > The package submission system is hostile and incredibly frustrating to use. > > I've tried a bazillion times now to submit a package (check-sexp-equal) and > ensure that: > > 1) the source points to a git repo properly: it keeps going

[racket] the current package submission system is a mess

2014-11-05 Thread Ryan Davis
The package submission system is hostile and incredibly frustrating to use. I've tried a bazillion times now to submit a package (check-sexp-equal) and ensure that: 1) the source points to a git repo properly: it keeps going to an https url and then fails on install because it doesn't have a MA