[Seaside] Setup Pier environment

[dtrussardi at tiscali.it]

Ciao 

	i report some data:

> Ciao Esteban,
> 
>> and which version of Pier are you trying to load?
> 
> 	i'm interested to load the last version which run into both Pier and Gemstone.
> 
> 	As Johan write:
> 
> 			In a previous email, I remarked that the Pier code does not seem to be ported to Seaside 3.1.x
> 			If you want to use Pier, use Seaside 3.0.x
> 
> 	Then i think the last stable version for Seaside 3.0.x.

	In Gemstone the last Seaside3		 3.0.x 			should be	3.0.13

		The relative Magritte3							should be 	3.0
	
		The relative 	Magritte3AddOns					should be 	3.0.0

		The relative Pier3 							should be 	3.0.0

		The relative Pier3AddOns						should be 	3.0.3
	
> 
> 	Thank,
> 
> 		Dario
>> 
>> (btw, the signup of ci.inria should be automatically approved so you should be able to log in fine)
>> 
>> Esteban
>> 
>>> On 22 Oct 2014, at 17:18, dtrussardi at tiscali.it wrote:
>>> 
>>> Ciao Stephan,
>>> 
>>> 	as you can see, i have some problem to test Pier into Pharo with Seaside 3.0.x
>>> 
>>> 	Perhaps no one cares, but I'd have to test Pier into Pharo and then check whether Pier run into Gemstone (GLASS).
>>> 
>>> 	I'm not expert to manage package and configurations.
>>> 
>>> 	But i'm very surprised of the complication i've met these days.
>>> 
>>> 	I have not clear idea about configurations but i think my last step  are correct !	 or Not ?
>>> 
>>> 	Is there some trick to load Pier version for seaside 3.0.x?
>>> 
>>>> Hi Dario,
>>>> 
>>>> There are ci builds of Pier and PierAddons on ci.inria.fr.
>>>> They are green, but not everything works. The easiest
>>>> way to make things work is to add red tests so you break
>>>> the build and then commit fixed versions and configurations.
>>>> If you don't know how to fix, just adding red tests already 
>>>> helps a lot. Just ask in the pharo-dev list for an ci account,
>>>> then you can log in and get a much better view on what
>>>> exactly is loaded and tested in a build. 
>>> 
>>> 	I do the sing-up   at ci.inria.fr 	but it don't answer.
>>>> 
>>>> What we are currently missing is tests that can pinpoint
>>>> the use of deprecated methods/classes. As you noticed,
>>>> most needed fixes are rather trivial.
>>>> 
>>>> Our Pier3 installation works, but of course does not use
>>>> all add-ons. We fixed the problems we encountered,
>>>> and will (sometimes slowly, we have a week of holidays
>>>> here) continue doing so. 
>>>> 
>>>> Do you plan on moving to a newer Pharo version soon?
>>> 
>>> As i write before i'm working to port some code from Pharo environment to GLASS.
>>> 
>>> So do not know if I'll have time, in the next week, to consider new versions if not directly involved in my work.
>>> 	
>>> 	Ciao,
>>> 
>>> 		Dario
>>> 	
>>>> 
>>>> Stephan
>>>> _______________________________________________
>>>> seaside mailing list
>>>> seaside at lists.squeakfoundation.org
>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>> 
>>> _______________________________________________
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>> 
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside