You got me...
Then I think current python26 is the best we can.
would like to break the other pythons to be built in this way...
On Sat, Jan 3, 2009 at 11:56 AM, Joshua Root wrote:
> Akira Kitada wrote:
>> I prefer the way how python26 is built now to python25's, mostly
>> because it eliminated
py*-setuptools, py*-ipython, py*-virtualenv, py*-django etc...
On Sat, Jan 3, 2009 at 11:04 AM, Ryan Schmidt wrote:
> On Jan 2, 2009, at 06:30, Akira Kitada wrote:
>
>> How should I avoid conflict when there are two or more ports
>> installing the same file to the same path?
>> For Python ports,
Akira Kitada wrote:
> I prefer the way how python26 is built now to python25's, mostly
> because it eliminated the need to specify
> "depends_lib-append port:py25-hashlib port:py25-zlib" again and again...
>
> I'm so happy with it and really hate the way it was in python25,
> and that's why I want
On Jan 2, 2009, at 06:30, Akira Kitada wrote:
How should I avoid conflict when there are two or more ports
installing the same file to the same path?
For Python ports, there seems to be a convension that a port that's
considered to be "default version" takes the name bin/foo,
and ones of other v
On Dec 31, 2008, at 12:26, Jean-Michel Pouré wrote:
As there is still no Kdenlive+MLT port, would someone be so kind to
provide SSH access to a MacOsX station, so I can prepare packages
myself.
Kdenlive is a really interesting software for video enthousiasts using
MacOsX and I don't understand
On Jan 2, 2009, at 13:17, David Evans wrote:
Jeremy Huddleston wrote:
On Jan 2, 2009, at 10:44, Adam Mercer wrote:
On Fri, Jan 2, 2009 at 18:18, wrote:
Revision 44730 Author jerem...@macports.org Date 2009-01-02
10:18:30
-0800
(Fri, 02 Jan 2009)
Log Message
cairo: Added missing dep o
On Fri, Jan 02, 2009 at 11:58:41AM -0800, Neil said:
[...]
>
> Why not just take advantage of variants?
>
> We could have python##, with three variants:
> minimal: just the basic python stuff (ie. python-core)
> normal: most, but not all, of the dependencies, as in FreeBSD
> full: a full standard
Jeremy Huddleston wrote:
>
> On Jan 2, 2009, at 10:44, Adam Mercer wrote:
>
>> On Fri, Jan 2, 2009 at 18:18, wrote:
>>> Revision 44730 Author jerem...@macports.org Date 2009-01-02 10:18:30
>>> -0800
>>> (Fri, 02 Jan 2009)
>>>
>>> Log Message
>>>
>>> cairo: Added missing dep on librsvg
>>
>> What
On Fri, Jan 02, 2009 at 11:48:09AM -0500, Randall Wood said:
> I would like to suggest the following:
>
> That for each version of python (pythonxy), there be the following ports:
>
> pythonxy, which installs nothing (maybe a readme file so that macports
> can consider it installed), but which de
On Jan 2, 2009, at 3:38 PM, Jeremy Huddleston wrote:
On Jan 2, 2009, at 10:44, Adam Mercer wrote:
On Fri, Jan 2, 2009 at 18:18, wrote:
Revision 44730 Author jerem...@macports.org Date 2009-01-02
10:18:30 -0800
(Fri, 02 Jan 2009)
Log Message
cairo: Added missing dep on librsvg
What d
On Jan 2, 2009, at 10:44, Adam Mercer wrote:
On Fri, Jan 2, 2009 at 18:18, wrote:
Revision 44730 Author jerem...@macports.org Date 2009-01-02
10:18:30 -0800
(Fri, 02 Jan 2009)
Log Message
cairo: Added missing dep on librsvg
What does this bring cario, as adding this brings in quite a f
On Fri, Jan 2, 2009 at 8:48 AM, Randall Wood
wrote:
> I would like to suggest the following:
>
> That for each version of python (pythonxy), there be the following ports:
>
> pythonxy, which installs nothing (maybe a readme file so that macports can
> consider it installed), but which depends on t
On Fri, Jan 2, 2009 at 18:18, wrote:
> Revision 44730 Author jerem...@macports.org Date 2009-01-02 10:18:30 -0800
> (Fri, 02 Jan 2009)
>
> Log Message
>
> cairo: Added missing dep on librsvg
What does this bring cario, as adding this brings in quite a few gnome packages?
Cheers
Adam
__
I would like to suggest the following:
That for each version of python (pythonxy), there be the following
ports:
pythonxy, which installs nothing (maybe a readme file so that macports
can consider it installed), but which depends on the following:
pythonxy-core, which is analogous to the
Hi,
How should I avoid conflict when there are two or more ports
installing the same file to the same path?
For Python ports, there seems to be a convension that a port that's
considered to be "default version" takes the name bin/foo,
and ones of other versions use bin/foo-x.y.
Is this still vali
I prefer the way how python26 is built now to python25's, mostly
because it eliminated the need to specify
"depends_lib-append port:py25-hashlib port:py25-zlib" again and again...
I'm so happy with it and really hate the way it was in python25,
and that's why I wanted it to be propagated to other
16 matches
Mail list logo