Jeremy Huddleston wrote:
> Does the XFree86 port actually function? It didn't even build last I
> tried (granted it was over a year ago, but there doesn't seem to have
> been much movement on the port)... and the xorg port is using a codebase
> from 3 years ago and hasn't been touched since 2007-0
Ryan Schmidt wrote:
>> I intend to go through all the x11 related ports and update
>> dependencies to be lib: or bin: where appropriate instead of port: (if
>> a port is not nomaintainer or openmaintainer, I will file a bug in
>> trac to be on the safe side... unless general consensus here is that
On Nov 22, 2008, at 22:54, Joshua Root wrote:
Ryan Schmidt wrote:
On Nov 22, 2008, at 23:09, Jeremy Huddleston wrote:
Oh and one more issue I just remembered... I've seen quite a few
ports
do:
prefix ${x11prefix}
This seems to be a clear violation of the "nothing in /usr"
policy...
and
On Nov 22, 2008, at 21:26, Ryan Schmidt wrote:
On Nov 22, 2008, at 23:00, Jeremy Huddleston wrote:
For those of you who don't know me, I took over development of X11
in OSX when Ben Byer moved on to bigger and better things at the
beginning of 2009.
S! I thought people weren't supposed
Ryan Schmidt wrote:
> On Nov 22, 2008, at 23:09, Jeremy Huddleston wrote:
>
>> Oh and one more issue I just remembered... I've seen quite a few ports
>> do:
>>
>> prefix ${x11prefix}
>>
>> This seems to be a clear violation of the "nothing in /usr" policy...
>> and as someone who feels some amount
On Nov 22, 2008, at 23:09, Jeremy Huddleston wrote:
Oh and one more issue I just remembered... I've seen quite a few
ports do:
prefix ${x11prefix}
This seems to be a clear violation of the "nothing in /usr"
policy... and as someone who feels some amount of ownership of /usr/
X11, I don't
On Nov 22, 2008, at 23:00, Jeremy Huddleston wrote:
For those of you who don't know me, I took over development of X11
in OSX when Ben Byer moved on to bigger and better things at the
beginning of 2009.
S! I thought people weren't supposed to know you have a time
machine. :)
I've
Oh and one more issue I just remembered... I've seen quite a few ports
do:
prefix ${x11prefix}
This seems to be a clear violation of the "nothing in /usr" policy...
and as someone who feels some amount of ownership of /usr/X11, I don't
want to see it get potentially thrashed...
Am I corr
For those of you who don't know me, I took over development of X11 in
OSX when Ben Byer moved on to bigger and better things at the
beginning of 2009. I've been poke, prodded, nudged, and otherwise
motivated into trying to "fix the X11 problem in Macports" as well...
so I figured I'd make
On Sat, Nov 22, 2008 at 04:54:06PM -0500, Luis O'Shea said:
> On Nov 22, 2008, at 4:35 PM, Bryan Blackburn wrote:
>
>> On Sat, Nov 22, 2008 at 02:44:27PM +0100, Simon Ruderich said:
>> [...]
>>>
>>> I tried to extract the patch from SVN and attached it to this mail. It
>>> builds
>>> fine for me o
On Nov 22, 2008, at 17:13, Perry Lee wrote:
Ryan Schmidt wrote:
Which PortGroup did you use?
I tried python and python24. At the time, I thought both groups were
returning the warning message, but it looks I was wrong about the
latter
(I just tried it again). Sorry, my bad.
Note there'
Ryan Schmidt wrote:
> Which PortGroup did you use?
I tried python and python24. At the time, I thought both groups were
returning the warning message, but it looks I was wrong about the latter
(I just tried it again). Sorry, my bad.
> Note there's currently this idea to consolidate the Python P
On Nov 22, 2008, at 16:39, Perry Lee wrote:
For new Python ports, what should the PortGroup be set to? I recently
noticed the warning message "Warning: This portgroup is deprecated and
will be removed in a future version!" while running a portindex.
Which PortGroup did you use?
Note there's
For new Python ports, what should the PortGroup be set to? I recently
noticed the warning message "Warning: This portgroup is deprecated and
will be removed in a future version!" while running a portindex.
Thanks,
Perry
___
macports-dev mailing list
ma
On Sat, Nov 22, 2008 at 02:44:27PM +0100, Simon Ruderich said:
[...]
>
> I tried to extract the patch from SVN and attached it to this mail. It builds
> fine for me on 10.4 but could you please test if it works on Leopard?
Nice, builds fine on 10.5.5 now. If Luis is okay with it, either Simon or
On Nov 22, 2008, at 11:49 AM, William Davis wrote:
re: http://trac.macports.org/wiki/InstallingMacPorts
I know told our former Release Engineer that the directions given on
this page concerning setting the DISPLAY env value were incorrect
for Mac OS 10.5 and later. He wrote me that he had
re: http://trac.macports.org/wiki/InstallingMacPorts
I know told our former Release Engineer that the directions given on
this page concerning setting the DISPLAY env value were incorrect for
Mac OS 10.5 and later. He wrote me that he had updated this. I just
reviewed the page and note tha
On Fri, Nov 21, 2008 at 04:01:15PM -0700, Bryan Blackburn wrote:
> Perhaps Simon was referring to just the bit in your comment about "It might
> be useful to factor out the version of the gc lib into its own variable (in
> a separate commit)."? At least I hope so, since the "Port Updates"
> milest
18 matches
Mail list logo
