Re: Port commit questions regarding python versions and philosophy for splitting ports

2010-10-30 Thread Ryan Schmidt
On Oct 29, 2010, at 10:19, Michelle Gill wrote: > On Oct 29, 2010, at 10:03 AM, Bradley Giesbrecht wrote: > >> You can always contribute new ports and patches using MacPorts Trac :) >> >> http://trac.macports.org/newticket > > I am aware of the trac system. Based on the MacPorts Guide, I thoug

Re: Port commit questions regarding python versions and philosophy for splitting ports

2010-10-29 Thread Michelle Gill
Hi Bradley, On Oct 29, 2010, at 10:03 AM, Bradley Giesbrecht wrote: > You can always contribute new ports and patches using MacPorts Trac :) > > http://trac.macports.org/newticket I am aware of the trac system. Based on the MacPorts Guide, I thought that commit rights were required for new po

Re: Port commit questions regarding python versions and philosophy for splitting ports

2010-10-29 Thread Bradley Giesbrecht
On Oct 29, 2010, at 5:50 AM, Michelle Gill wrote: Hi Daniel, Thank you so much for the reply. On Oct 28, 2010, at 10:41 AM, Daniel J. Luke wrote: On Oct 28, 2010, at 9:17 AM, Michelle Gill wrote: * When building python packages (or any package where there are multiple versions maintaine

Re: Port commit questions regarding python versions and philosophy for splitting ports

2010-10-29 Thread Michelle Gill
Hi Daniel, Thank you so much for the reply. On Oct 28, 2010, at 10:41 AM, Daniel J. Luke wrote: > On Oct 28, 2010, at 9:17 AM, Michelle Gill wrote: >> >> * When building python packages (or any package where there are multiple >> versions maintained), does one have to build to support all vers

Re: Port commit questions regarding python versions and philosophy for splitting ports

2010-10-28 Thread Daniel J. Luke
On Oct 28, 2010, at 9:17 AM, Michelle Gill wrote: > > * When building python packages (or any package where there are multiple > versions maintained), does one have to build to support all versions? I only > have python 2.6 on my system right now. Would I need to install python 2.5 > (and 2.7,