On Aug 30, 2010, at 12:27 PM, Jeff Singleton wrote:
So there is no way to avoid building the truckload of X dependencies
needed for a single application...followed by cleaning up all of those
dependencies because I only needed them to build one thing.
Yes, create your own Portfile or modify the MacPorts provided one.
To me .. that just doesn't sound like consistent support for older
machines ... it sounds lazy.
So the MacPorts volunteers are lazy. I see. Not to be mean but maybe
you could do something about it.
Why should people with faster machines have to continually suffer lost
time in building dependencies that are only needed temporarily or
could be provided by the XQuartz package? I can understand building
dependencies that are not included in the XQuartz package, but
building all of them just because its more compatible with older
hardware that I will never use...
Just doesn't make sense to me ... If I had a dual quad-core 32gig Mac
Pro, I probably wouldn't care.
There are tradeoffs. Supporting the use of XQuartz would add to the
overall support burden. You can always modify the Portfile to your
liking.
http://trac.macports.org/wiki/FAQ#ownlibs
http://trac.macports.org/wiki/FAQ#whynotxyz
// Brad
On Mon, Aug 30, 2010 at 3:04 PM, Jeremy Huddleston
<[email protected]> wrote:
On Aug 30, 2010, at 10:43, Jeff Singleton wrote:
Ok .. So what if I opted to not install the system X11 and then
installed XQuartz from MacOSForge via DMG. Could I just make some
Env
Variables to point Libs/Includes/Path for X11 to /opt/X11?
As mentioned, in the link below, MacPorts will use its own copies
of libraries where available. This is not just limited to X11 and
includes other libraries like libcurl, ncurses, bzip2, zlip, ...
You are free to use whatever X11 server you want (meaning /
Applications/Utilities/XQuartz.app or /Applications/MacPorts/X11.app)
On Mon, Aug 30, 2010 at 10:23 AM, Brandon S Allbery KF8NH
<[email protected]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 8/30/10 08:30 , Jeff Singleton wrote:
I hope this can be just a quick one ...
Can Macports be forced to used the XQuartz release installed by
DMG,
instead of painfully going through the build process of every
single X
dependency?
It's a quick one, but not the way you hope.
http://trac.macports.org/wiki/FAQ#x11-libs
- --
brandon s. allbery [linux,solaris,freebsd,perl] [email protected]
system administrator [openafs,heimdal,too many hats] [email protected]
electrical and computer engineering, carnegie mellon
university KF8NH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkx7vsgACgkQIn7hlCsL25VDqwCguD5lhT7X6DicNOdg0U9W3lKT
eTQAni5vx4gc5j7QOPQWgqYqaDZMJVAL
=OcnH
-----END PGP SIGNATURE-----
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
