About 3.6 alpha process: to break the less

Stephane Ducasse ducasse at iam.unibe.ch
Wed Jun 4 12:07:35 UTC 2003


On Wednesday, June 4, 2003, at 03:04 PM, Daniel Vainsencher wrote:

> Loading this package reloads all the packages unloads. If you want to
> work on a Full image, as you stated, this will help.
>
> I've stated before that I don't think that's the solution - I think 
> that
> refactoring an image with any subset of SM package will break some
> stuff. Working in Full will make you generate patches to lots of
> packages. This is good, if you intend to help the maintainer of each
> package integrate it. Otherwise, it's a waste of time.
>

OK


> Either way, don't feel free to deprecate anything you don't think is
> used, because you *don't* have a closed world. Give consideration to
> what you remove/deprecate.
Don't be worry about that. we do not deprecate things because they are 
not use.
We deprecate them because they are not at the right place.


>
> Daniel
>
> Stephane Ducasse <ducasse at iam.unibe.ch> wrote:
>> Hi daniel
>>
>> I'm a bit lost. Should I load this package in 3.6 before my KCP 
>> changes
>> then I can produce different changesets for each removal?
>>
>> Stef
>>
>> On Wednesday, June 4, 2003, at 02:17 PM, Daniel Vainsencher wrote:
>>
>>> Just wanted to note that this is exactly what the SM package "Upgrade
>>> to
>>> 3.6 Full Image" does. Doug did this a few weeks back.
>>>
>>> Daniel
>>>
>>> Tim Rowledge <tim at sumeru.stanford.edu> wrote:
>>>> One relatively simple tool I can see a use for is just the set of
>>>> scripts to produce the currently dropped out packages; not the 
>>>> removal
>>>> of the code, which we already have but the production of the stuff 
>>>> to
>>>> file back in.
>>>
>



More information about the Squeak-dev mailing list