Hi,
I documented Snapshotcello here:
http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-ready
http://www.tudorgirba.com/blog/snappier-snapshotcello
In short, the reason for Snapshotcello is to deal with deeply nested
configurations, like we have in Moose, in a reliable way.
> Am 09.11.2013 um 22:04 schrieb Tudor Girba :
>
> There is a very easy way. Create a configuration version that explicitly
> specify the package versions without Snapshotcello.
>
There is still version 1.6 that is made that way. I tried using it with
Versionner but that doesn't work. I load
There is a very easy way. Create a configuration version that explicitly
specify the package versions without Snapshotcello.
Doru
On Sat, Nov 9, 2013 at 3:38 PM, Norbert Hartl wrote:
>
>
> Am 09.11.2013 um 12:21 schrieb Stéphane Ducasse >:
>
> Indeed.
> I see
> and I did not got the time to f
> Am 09.11.2013 um 12:21 schrieb Stéphane Ducasse :
>
> Indeed.
> I see
> and I did not got the time to fix the issue I saw when applying on private
> projects.
>
>> Agreed. But, the ConfigurationOfPetitParser is up to date. It has groups to
>> distinguish between between core and gui.
>>
>>
Indeed.
I see
and I did not got the time to fix the issue I saw when applying on private
projects.
> Agreed. But, the ConfigurationOfPetitParser is up to date. It has groups to
> distinguish between between core and gui.
>
> The only problem that Norbert raised is that when using Snapshotcello,
Agreed. But, the ConfigurationOfPetitParser is up to date. It has groups to
distinguish between between core and gui.
The only problem that Norbert raised is that when using Snapshotcello, the
groups are lost due to flattening of the entire configuration.
Doru
On Sat, Nov 9, 2013 at 2:12 AM, St
Guys
even if one day we may integrate petitparser (so far I do not see why - but do
not comment). We need an up to date configuration
because we want everything with configuration because we want to bootstrap 4.0.
Stef
People
can you remove the one you do not use and we keep the one of Moose?
On Nov 7, 2013, at 10:10 AM, Norbert Hartl wrote:
> Looking at smalltalkhub there are plenty of PetitParser repos to find but
> none that looks official. So which is considered official? I still had Lukas’
> repo in m
Am 07.11.2013 um 16:25 schrieb Tudor Girba :
> Hi,
>
>
> On Thu, Nov 7, 2013 at 3:39 PM, Norbert Hartl wrote:
> Btw. how is the ConfigurationOfPetitParser supposed to work? I loaded the one
> from the moose repo. Looking at it I need to use at least 1.6 because earlier
> versions have still
Hi,
On Thu, Nov 7, 2013 at 3:39 PM, Norbert Hartl wrote:
> Btw. how is the ConfigurationOfPetitParser supposed to work? I loaded the
> one from the moose repo. Looking at it I need to use at least 1.6 because
> earlier versions have still Lukas’ repositories configured. But if I load
> 1.6 and
Btw. how is the ConfigurationOfPetitParser supposed to work? I loaded the one
from the moose repo. Looking at it I need to use at least 1.6 because earlier
versions have still Lukas’ repositories configured. But if I load 1.6 and try
to use Versionner it shows me that I have 1.8-snapshot loaded.
> Am 07.11.2013 um 12:12 schrieb Tudor Girba :
>
> Hi,
>
> I think you missed my point. I know I can technically load the code from
> multiple places :).
>
I know you know. I couldn't miss the point because for me there is none :)
> For Moose, PetitParser is an important component that is bei
Hi,
I think you missed my point. I know I can technically load the code from
multiple places :).
For Moose, PetitParser is an important component that is being developed by
the team. Up to now, we did that, hence it made perfect sense to have it in
the Moose team repository and in our responsibil
Am 07.11.2013 um 11:46 schrieb Tudor Girba :
> Hi,
>
> It is in the Moose repository because Moose was essentially the first larger
> user (besides Helvetia) since its inception (more than 3 years now), and
> because the development of PetitParser was taken care of by the Moose team.
>
Being
Hi,
It is in the Moose repository because Moose was essentially the first
larger user (besides Helvetia) since its inception (more than 3 years now),
and because the development of PetitParser was taken care of by the Moose
team.
If others want to contribute (and even integrate into Pharo), it wo
Am 07.11.2013 um 11:07 schrieb Stephan Eggermont :
> The official repository of PetitParser is
> Moose/PetitParser
> on smalltalkhub
>
thanks.
> http://forum.world.st/moving-petitparser-to-smalltalkhub-td4671840.html
>
Well, this is not a good place IMHO. A more independent but official repo w
The official repository of PetitParser is
Moose/PetitParser
on smalltalkhub
http://forum.world.st/moving-petitparser-to-smalltalkhub-td4671840.html
Hi,
https://ci.inria.fr/moose/job/petitparser/
Or PBE2 says:
Gofer new
smalltalkhubUser: 'Moose' project: 'PetitParser';
package: 'ConfigurationOfPetitParser';
load.
(Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault.
Hope it helps, I use the first option.
Cheers,
Jan
On Thu, N
If we open an official one, given the importance of petitparser, it should be
under PharoExtras.
On 2013-11-07, at 10:10, Norbert Hartl wrote:
> Looking at smalltalkhub there are plenty of PetitParser repos to find but
> none that looks official. So which is considered official? I still had Lu
19 matches
Mail list logo
