[Cuis-dev] Converting Tonel packages

Phil B pbpublist at gmail.com
Wed Jul 31 12:21:58 PDT 2019


That's a generous offer and hopefully someone will be attending to take you
up on it.[1]  In the meantime, a quick search returns what appears to be at
least a partial summary of FileTree vs Tonel:
https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/ExportFormats.md

[1] While it would help ensure a better understanding of how things
developed, I'm not sure it would actually change anything. There has been
difference of opinion between the Cuis and Squeak/Pharo communities pretty
much since day 1 on the subject of package formats, among other things.  My
take is that the lack of convergence on a common solution is due to
fundamental philosophical, rather than technical, differences.

On Wed, Jul 31, 2019 at 2:50 PM Dale Henrichs via Cuis-dev <
cuis-dev at lists.cuis.st> wrote:

> I've been following this particular issue and would prefer not to get into
> an email-based discussion of why tonel/filetree came to be and their
> relative disadvantages and advantages ...
>
> However, I will be at ESUG in Cologne and would love to have a discussion
> (at a whiteboard) with one or more members of the Cuis community to talk
> things over and see if there is any common ground to be found ...
>
> Dale
> On 7/31/19 10:18 AM, Phil B via Cuis-dev wrote:
>
> On Wed, Jul 31, 2019 at 9:54 AM Juan Vuletich via Cuis-dev <
> cuis-dev at lists.cuis.st> wrote:
>
>> pufff.
>>
>> I don't want to even think of how github package diff would look like.
>>
>> At least they could use xxx.filetree.st and xxx.tonel.st (like we use
>> xxx.pck.st and xxx.cs.st). Now it is impossible for tools to tell
>> whether they are dealing wiht filetree, tonel, or some other smalltalk
>> format...
>>
>>
> They use .properties files to convey that information.  Actually I think
> the entire point of these 'exploded' package formats was to make raw
> method-level diffs pretty... at the cost of making the overall package
> format quite ugly/cumbersome.   Every time I've had to look at a repo using
> those formats, I'm happy you went the direction you did with package
> files.  You prioritized the people using the package files, they continue
> to prioritize the tools that manipulate them.
>
>>
>>
> --
> Cuis-dev mailing list
> Cuis-dev at lists.cuis.st
> https://lists.cuis.st/mailman/listinfo/cuis-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20190731/807d8652/attachment.htm>


More information about the Cuis-dev mailing list