Le 07-04-25 à 19:50, Ben Byer a écrit :
On Apr 18, 2007, at 2:40 PM, Yves de Champlain wrote:
Le 07-04-18 à 16:10, Jordan K. Hubbard a écrit :
Just to follow up to myself, by "we" I mean Apple. I'm not clear
on what MacPorts wants to do just yet given that the xorg port
doesn't have a maintainer.
Maybe I can convince the guy maintaining Apple's X11 to also
maintain MacPorts' x11, but I make no promises. :-)
The guy seems to be heading the good way :
http://gitweb.freedesktop.org/?p=users/bbyer/dports.git;a=tree
*delurk*
Being curious by nature, what does this mean ?
I'd like to eventually submit these for inclusion in MacPorts to
replace the broken xorg port that currently exists. As it stands,
I wasn't able to figure out how to build more than one module (each
of which needs a separate configure / make / make install step) per
portfile, so I have dozens of dozens of portfiles out there.
Building a replacement for X11.app takes > 200 modules, and I don't
really want to dump that many portfiles into the main collection.
Being curious by nature, isn't it the goal of modular x11, to be be
modular ? just asking.
yves
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
