On 4 January 2013 08:02, H. Hirzel <hannes.hirzel at gmail.com> wrote:
> The problem is that Jeff does not have the right to do that

Yes, and I can't help with that.

> and he
> likes to have some guidance....

I thought that's what I did? "Don't edit the release, make a new one instead" :)

I don't know how to handle versioning things for packages that work in
multiple images, but perhaps Dave can suggest something? OSProcess has
had to work across multiple Squeaks for ages.

frank

> --Hannes
>
> On 1/4/13, Frank Shearar <frank.shearar at gmail.com> wrote:
>> On 4 January 2013 06:15, Jeff Gonis <jeff.gonis at gmail.com> wrote:
>>> Hi Squeak-Dev,
>>>
>>> So one of the things that I can't live without in my image is
>>> auto-completion as provided by OComplete.  Levente made a release for
>>> Squeak
>>> 4.2, and it has worked in every release since then but the package has
>>> not
>>> been updated to indicate this.  In addition, the "extending the
>>> workspace"
>>> code that allows for the installation of OComplete triggers a debugger
>>> when
>>> it calls Smalltalk at: ECToolSet, as this key cannot be found.  However,
>>> installing the Squeak 4.2 compatible version from SqueakMap does work
>>> nicely
>>> in 4.4.
>>>
>>> The OComplete package is not listed as community supported, so I don't
>>> believe that I can edit it, although I get the full interface when I
>>> right-click on the package and select "Edit Release".
>>>
>>> So I have two questions:
>>>
>>> 1) Can we make OCompletion into a Community Supported Package?  I believe
>>> that it provides considerable benefits when developing in Squeak
>>>
>>> 2) Once it is community supported, do I just select "Edit Release" on the
>>> 4.2 compatible release, change the compatibility level to Squeak 4.4,
>>> update
>>> the name and enter my squeak map id/password?  I want to get some
>>> experience
>>> doing this, but I'd rather not learn by doing it wrong the first time and
>>> ending up with some egg on my face.
>>
>> I think it would be more appropriate to make a _new_ release for 4.4
>> (which is just as easy as editing a release).
>>
>> frank
>>
>>> Maybe a bit of a tutorial on how to go about editing a community
>>> supported
>>> package would be helpful.
>>>
>>> Thanks for your help,
>>> Jeff G.
>>
>>
>