If you run `Pkg.register("YourPkgName")` at the Julia REPL, it will
generate that folder for you (complete with the commit hashes).

Does that work for you?


On Fri, Sep 5, 2014 at 9:06 AM, Samuel S. Watson <[email protected]>
wrote:

> OK, that's a fair point. What I should have said is that my interpretation
> of what he said wasn't the right thing to do. It hinges on what stuff is
> supposed to be added to the directory. I had assumed it was the package
> stuff, and in fact it's supposed to be a directory containing some version
> information and a url. I can see why my original interpretation doesn't
> make sense. Nevertheless, it seems to me that the step of
> finding/generating this package metadata directory is nontrivial (e.g., it
> includes some long alphanumeric string). Can someone fill me in?
>
> On Friday, September 5, 2014 9:39:45 AM UTC-4, Jacob Quinn wrote:
>>
>> "wasn't the right thing to do"...
>>
>> I don't think I'd say that. It's essentially what Pkg.publish() is doing
>> underneath anyway (or tries to do). The steps he listed are actually how I
>> bump packages all the time, since I've had troubles with Pkg.publish() as
>> well.
>>
>> -Jacob
>>
>>
>> On Fri, Sep 5, 2014 at 9:36 AM, Samuel S. Watson <[email protected]>
>> wrote:
>>
>>> For the record, I tried Mauro's suggestion, and it worked but it wasn't
>>> the right thing to do. And the step where I'm stuck is Pkg.publish(), not
>>> Pkg.register(). That's the one that the documentation says often breaks,
>>> and it also doesn't take any arguments, which makes me think it's going to
>>> publish all my registered packages, which I'm not ready to do.
>>>
>>>>
>>>>
>>

Reply via email to