[squeak-dev] Move Chronology out of Kernel and into its own Chronology package (was: trunk thinks its tomorrow)

Levente Uzonyi leves at caesar.elte.hu
Mon Feb 29 23:14:15 UTC 2016

For some reason the mails have only arrived to the packages list:


On Sat, 27 Feb 2016, David T. Lewis wrote:

> On Mon, Feb 22, 2016 at 02:38:43PM -0800, Bert Freudenberg wrote:
>> On 21.02.2016, at 10:36, Chris Muller <asqueaker at gmail.com> wrote:
>>> On Sat, Feb 20, 2016 at 7:35 PM, David T. Lewis <lewis at mail.msen.com> wrote:
>>>> On Thu, Feb 18, 2016 at 11:54:44AM -0600, Chris Muller wrote:
>>>>> I have no problem if you want move Chronology classes to their own
>>>>> package (but please do use the "-Core" and "-Tests" suffixes so we
>>>>> don't suffer the prefix selection problem).  I'll be curious whether
>>>>> you choose to move Date and Time too..
>>>> I need some guidance on package naming.
>>>> We have packages named 'Kernel' and  'KernelTests', 'Morphic' and
>>>> 'MorphicTests', and 'Collections' and 'CollectionsTests'. Based on
>>>> this, I would expect that 'Chronology' and 'ChronologyTests' would
>>>> be good package names.
>>>> Is that right? Or should it instead be 'Chronology-Core' and
>>>> 'Chronology-Tests'?
>>> Note we also have packages named Regex-Core, Regex-Tests,
>>> SqueakSSL-Core, SqueakSSL-Tests, WebClient-Core, WebClient-Tests,
>>> which were (formerly) external packages.  You want to make Chronology
>>> more like an external package, so it can be swapped out more easily.
>>> "-Core" brings a clarity to the core unit's modular boundary, while
>>> being consistent with the number of levels in each package name that
>>> comprises that system.
>> Agree with Chris.
>> - Bert -
> I am not seeing the update notices on the mailing list, but I just did
> the move of Kernel-Chronology to Chronology-Core and KernelTests-Chronology
> to Chronology-Tests, with update-dtl.349.mcm to add the new packages. All
> seems well and I can update an earlier image from the stream.
> Dave

More information about the Squeak-dev mailing list