[Pharo-users] [ANN] SETT (Store Export to Tonel Tools) for Pharo6.1

Esteban Maringolo emaringolo at gmail.com
Tue Feb 19 19:36:19 EST 2019


I tried to test SETT to migrate a Package from Store to our repo.

But it fails while initializing the git repository. I set the destination
config to `isNewRepository := false`, then it works as expected.

I'm testing it against the Cincom Public Repository, which being remote and
full of code (and garbage), limiting by date isn't useful if I can't filter
by a particular package name/pattern (I couldn't find such option).

In any case, it's a helpful tool to ease the migration of code.


Esteban A. Maringolo

El mié., 16 ene. 2019 a las 18:18, Dale Henrichs via Pharo-users (<
pharo-users at lists.pharo.org>) escribió:

> On 1/16/19 11:56 AM, Esteban Maringolo wrote:
> This is great!
> One less fence to move code from one dialect to another. :)
> I will follow the examples and try to export code from Store and load id
> in Pharo.
> Is it mandatory to use Linux?
> We've only tested with Linux and it looks like the current code base is
> wired to use Unix[1] ....
> Dale
> [1]
> https://github.com/GemTalk/SETT/blob/master/StoreImporter.package/SettGitRepository.class/instance/runGitWithArguments..st
> Esteban A. Maringolo
> El mié., 16 ene. 2019 a las 16:38, Dale Henrichs (<
> dale.henrichs at gemtalksystems.com>) escribió:
>> GemTalkSystems is pleased to announce SETT (Store Export to Tonel
>> Tools)[1]. SETT is open source project with an MIT license.
>> SETT (Store Export to Tonel Tools) is a set of tools to export Smalltalk
>> code from Store and
>> write into the Tonel file format managed using Git.
>> SETT is:
>>    - a Pharo 6.1 application, that
>>    - connects to a Postgres Database
>>    - containing source code history in VisualWorks Store format; and
>>    - writes to a Git repository
>>    - in Tonel format
>>    - maintaining all version history, source code and SCM metadata.
>> SETT was developed last year to support one of our commercial customers
>> in their conversion From Store to Rowan[2]. Rowan artifacts are produced as
>> part of the output of SETT, but the Rowan artifacts can be ignored. The
>> important bit is that SETT converts from Store to Tonel and maintains
>> version history in git.
>> Please see the project ReadMe[3] and Wiki[4] for additional details.
>> Dale
>> [1] https://github.com/GemTalk/SETT
>> [2] https://github.com/GemTalk/Rowan
>> [3] https://github.com/GemTalk/SETT#overview
>> [4] https://github.com/GemTalk/SETT/wiki
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/attachments/20190219/1e614ad8/attachment-0001.html>

More information about the Pharo-users mailing list