[etoys-dev] Etoys: DrGeoII-Core-HilaireFernandes.16.mcz

[Bert Freudenberg]

On 19.06.2010, at 19:58, Bert Freudenberg wrote:

> Because that doesn't solve the problem, and creates extra work for us. Also, you are surely testing in the Etoys image anyway, right?
> 
> You simply need to copy your latest version to etoys. It's one click in Monticello on the "copy" button.
> 
> If you always do this, instead of saving a separate version for etoys, you will never run into this problem again.
> 
> - Bert -

Besides, your upstream version is licensed as LGPL. Only you as the author can release it under a different license. By publishing the package to the Etoys inbox you assert that you have the full rights to dual-license it as MIT.

Of course, that also means that you cannot relicense patches that someone else contributes to your code under the LGPL (unless that contributor would also release them under MIT for Etoys).

- Bert -

> On 19.06.2010, at 19:30, Hilaire Fernandes wrote:
> 
>> This multirepository for identic source code is unsane.
>> Why can't you just grab a copy from the upsteam repository when I notice one for you?
>> 
>> Hilaire
>> 
>> 
>> Bert Freudenberg a écrit :
>>> On 19.06.2010, at 19:01, Bert Freudenberg wrote:
>>>> On 19.06.2010, at 17:28, Hilaire Fernandes wrote:
>>>> 
>>>>> Hi Bert,
>>>>> 
>>>>> I can't see duplicated #12 package.
>>>>> What I see is jump in version number in the Etoys repository. For example, DrGeoII-core version jumped from #12 to #15. It is expected as the development is done in the DrGeo repository, then when I am happy with the changed code, I push a new version in DrGeo repository.
>>>>> 
>>>>> What else?
>>>>> Hilaire
>>>> You published a version 12 in the etoys repo, dated June 2.
>>>> 
>>>> On June 15, you took version 11 and started developing again, from that branch you published the current version.
>>>> 
>>>> So the current version does not have the original version 12 as a direct ancestor - that's where the problems come from. No automatic loading or merging is possible if a later version is not a child/grandchild of the previous version.
>>>> 
>>>> So this is breaking the automatic updating. You should always develop on a single version - branching takes extra effort.
>>>> 
>>>> - Bert -
>>> What you should do is merge the version 12 from the etoys repo into your latest version. Then publish that as a new version to your own repository, and *copy* it to the etoys repository (do not save it again).
>>> - Bert -
>> 
> 
> 
> _______________________________________________
> etoys-dev mailing list
> etoys-dev at squeakland.org
> http://lists.squeakland.org/mailman/listinfo/etoys-dev