[racket] Error installing planet-neil-csv2

Ah, yeah, thanks. I see that the change that fixed that problem wasn't
in 6.0.1. Sorry for the inconvenience.

Robby

On Tue, Jul 8, 2014 at 10:40 PM, Brian Adkins <racketusers at lojic.com> wrote:
> I clicked:
>
> "File" menu
> "Package Manager..." menu item
> "Available from Catalog" tab
> "Update Package List" button
>
> Then I selected the planet-neil-csv2 package from the list and clicked the Install button.
>
> --
> Brian Adkins
> Lojic Technologies, LLC
> http://lojic.com/
>
> On Jul 8, 2014, at 11:32 PM, Robby Findler wrote:
>
>> Oh, can you say more precisely exactly which places you clicked?
>> Probably I missed adding that flag somewhere in one of the paths thru
>> the GUI.
>>
>> Thanks,
>> Robby
>>
>> On Tue, Jul 8, 2014 at 10:24 PM, Brian Adkins <racketusers at lojic.com> wrote:
>>> Yes, I see "--deps search-auto". It may have worked had I installed via "Install Package" instead of via the Package Manager. For the next package, I'll try the Install Package dialog.
>>>
>>> --
>>> Brian Adkins
>>> Lojic Technologies, LLC
>>> http://lojic.com/
>>>
>>> On Jul 8, 2014, at 11:12 PM, Robby Findler wrote:
>>>
>>>> I believe it was fixed in 9ec766f, which seems to be dated before the
>>>> release, but it could have happened after the release branch was
>>>> created, I suppose.
>>>>
>>>> When you open the install package dialog and click the appropriate
>>>> checkboxes and type the name the way that you intended, if you click
>>>> on "show details" you should see a section labelled "Equivalent
>>>> command line invocation:" and that should have "--deps search-auto"
>>>> listed there.
>>>>
>>>> Do you see that?
>>>>
>>>> Robby
>>>>
>>>> On Tue, Jul 8, 2014 at 8:34 PM, Brian Adkins <racketusers at lojic.com> wrote:
>>>>> On Jul 8, 2014, at 9:29 PM, Robby Findler wrote:
>>>>>
>>>>>> I believe the "cannot respond to the prompt" problem has been fixed in
>>>>>> DrRacket (it just doesn't ask you anymore).
>>>>>>
>>>>>> Robby
>>>>>
>>>>> I'm running the 6.0.1 and "check for updates" states it's the latest. Maybe it's fixed in the latest source, but not released yet?
>>>>>
>>>
>