On Feb 25, 2011, at 11:37, narf...@macports.org wrote:
> Revision: 76487
> http://trac.macports.org/changeset/76487
> Author: narf...@macports.org
> Date: 2011-02-25 09:37:19 -0800 (Fri, 25 Feb 2011)
> Log Message:
> ---
> Added notice for bug #23298.
>
> Modified Paths:
>
On 2011-2-26 10:42 , Ryan Schmidt wrote:
> I did not think that glib2 required a dependency on python_select or a
> specific python port, but the dependency on the former was added in r45190
> [1]; see #17530 [2]. Guidance on what should be done here would be
> appreciated.
>
> [1] https://tra
On Feb 25, 2011, at 15:07, Joshua Root wrote:
> On 2011-2-25 16:03 , Ryan Schmidt wrote:
>> Second, the a problem with this strategy in the first place is that you're
>> declaring a dependency on the binary "python", and telling MacPorts to
>> install python_select if it can't find one, and then
On 2011-2-25 16:03 , Ryan Schmidt wrote:
> Second, the a problem with this strategy in the first place is that you're
> declaring a dependency on the binary "python", and telling MacPorts to
> install python_select if it can't find one, and then making the scripts run
> "/opt/local/bin/python".
Well I posted the ticket 10 months' ago. It was complete coincidence that
someone else posted a patch within 5 minutes of me running into this issue
again.
I did read the docs on that; the reason I didn't send in a patch originally is
that I thought the maintainer might have a better idea as to
I have created a patch for syck (updating from 0.55 to 0.70). I submitted it 10
months ago and no action has been taken.
https://trac.macports.org/ticket/24604
I am requesting that you commit the changes to the official repo as the current
0.55 version, when built on 10.6, is very buggy and cau
On Fri, Feb 25, 2011 at 12:03 AM, Ryan Schmidt wrote:
> On Feb 24, 2011, at 15:58, singingwolf...@macports.org wrote:
>
> > Revision: 76478
> > http://trac.macports.org/changeset/76478
> > Author: singingwolf...@macports.org
> > Date: 2011-02-24 13:58:33 -0800 (Thu, 24 Feb 2011)
> >
Thanks for the answer.
> Yes, as Mac OS X is a multi-user system we cannot write to the home
> directory of the user as this would not make it work for all users.
>
> Is there no global equivalent of this preferences file?
It is true that this is a problem. However, this seems to be specific to
