Re: [22092] trunk/dports/python

2007-02-21 Thread Jyrki Wahlstedt
On 18.2.2007, at 19.39, Markus Weissmann wrote: On 18.02.2007, at 17:47, Yves de Champlain wrote: Le 07-02-17 à 14:15, Blair Zajac a écrit : Yves de Champlain wrote: Le 07-02-17 à 11:32, Yves de Champlain a écrit : Le 07-02-17 à 11:18, [EMAIL PROTECTED] a écr

Re: Python 2.5 and py-crypto...

2007-02-21 Thread Blair Zajac
Randall Wood wrote: On 21 Feb 2007, at 20:43, Landon Fuller wrote: On Feb 21, 2007, at 15:43, Weissmann Markus wrote: Hi Douglas, the soon-to-be-released version 1.4 of port will come with a python 2.5 "port group". This will allow us to quickly produce all the python vastness for python

Re: Python 2.5 and py-crypto...

2007-02-21 Thread Randall Wood
On 21 Feb 2007, at 20:43, Landon Fuller wrote: On Feb 21, 2007, at 15:43, Weissmann Markus wrote: Hi Douglas, the soon-to-be-released version 1.4 of port will come with a python 2.5 "port group". This will allow us to quickly produce all the python vastness for python 2.5, too. This mig

Re: Python 2.5 and py-crypto...

2007-02-21 Thread Landon Fuller
On Feb 21, 2007, at 15:43, Weissmann Markus wrote: Hi Douglas, the soon-to-be-released version 1.4 of port will come with a python 2.5 "port group". This will allow us to quickly produce all the python vastness for python 2.5, too. This might be a chance for newcomers to start coding Portf

Re: Python 2.5 and py-crypto...

2007-02-21 Thread Weissmann Markus
Hi Douglas, the soon-to-be-released version 1.4 of port will come with a python 2.5 "port group". This will allow us to quickly produce all the python vastness for python 2.5, too. This might be a chance for newcomers to start coding Portfiles: Basically you will have to replace the "GroupC

Fwd: [22198] branches/release_1_4/

2007-02-21 Thread Juan Manuel Palacios
Good day to everyone! Well, the quoted message below pretty much says it all, I created a 1.4 branch for our next release so we can start testing rc's. The way I see it, there's only a handful of documentation updates left to include, which we can commit to both trunk and the branch, so I'd