Re: /etc/paths
On Feb 6, 2015, at 2:09 PM, Lawrence Velázquez wrote: > (1) We consider /etc/paths to be a "system file". We don't like modifying > system files. > (2) Modifying /etc/paths affects all users' settings, which is undesirable. Actually it is desirable, or it has at least been desired by some users, e.g.: https://trac.macports.org/ticket/36323 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
> (1) We consider /etc/paths to be a "system file". We don't like modifying > system files. Undertstood; I was thinking of the /etc/paths.d directory. > (2) Modifying /etc/paths affects all users' settings, which is undesirable. Ahh ... Very good. Not all users will want that. > > vq --- Entertaining minecraft videos http://YouTube.com/keybounce ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On Feb 6, 2015, at 1:49 PM, Michael wrote: > On 2015-02-06, at 10:25 AM, Luc Bourhis wrote: > >> Not launchd, no. It's for the shell and it helps with MANPATH too. "man >> path_helper" for the details. > > Interesting. I'm surprised MacPorts doesn't stuff something in there. (1) We consider /etc/paths to be a "system file". We don't like modifying system files. (2) Modifying /etc/paths affects all users' settings, which is undesirable. vq ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On Fri, Feb 6, 2015 at 1:49 PM, Michael wrote: > Interesting. I'm surprised MacPorts doesn't stuff something in there. In the past, it forced paths from /etc/paths after the system ones, whereas people tend to want MacPorts installs to override system ones. I don't know if this is still true. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On 2015-02-06, at 10:25 AM, Luc Bourhis wrote: > > On 6 Feb 2015, at 19:21, Michael wrote: > >>> Shame on me! You are right. This is a new computer and /etc/paths did not >>> get copied from the old one as I thought. Sorry for the noise and thanks for >>> your patience! >> >> /etc/paths? >> This is the first I've seen any indication of this. Where is this documented? >> Is this the apple-approved way to add stuff to PATH for programs run by >> launchD? > > Not launchd, no. It's for the shell and it helps with MANPATH too. "man > path_helper" for the details. Interesting. I'm surprised MacPorts doesn't stuff something in there. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On Fri, 6 Feb 2015, Michael wrote: > /etc/paths? This is the first I've seen any indication of this. Where is > this documented? Is this the apple-approved way to add stuff to PATH for > programs run by launchD? And what other little secrets are there? I've learned more about OSX from reading this list than from anywhere else, and I go back Unix-wise for 40 years! I have the Big Dummies ebook, but I'd like to see a Guru's Guide... -- Dave Horsfall DTM (VK2KFU) "Bliss is a MacBook with a FreeBSD server." http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: /etc/paths
On 6 Feb 2015, at 19:21, Michael wrote: >> Shame on me! You are right. This is a new computer and /etc/paths did not >> get copied from the old one as I thought. Sorry for the noise and thanks for >> your patience! > > /etc/paths? > This is the first I've seen any indication of this. Where is this documented? > Is this the apple-approved way to add stuff to PATH for programs run by > launchD? Not launchd, no. It's for the shell and it helps with MANPATH too. "man path_helper" for the details. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
/etc/paths
>Shame on me! You are right. This is a new computer and /etc/paths did not > get copied from the old one as I thought. Sorry for the noise and thanks for > your patience! /etc/paths? This is the first I've seen any indication of this. Where is this documented? Is this the apple-approved way to add stuff to PATH for programs run by launchD? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Mono -- does it really need X11?
On Friday February 06 2015 09:24:56 Michael wrote: > Mono's library dependencies: > Library Dependencies: gettext, glib2, libiconv, zlib, libgdiplus, xorg-libX11 If mono depends on X11 directly and not through GTk2, then it won't be as easy to avoid the dependency as I thought ... > And, Gtk2 also has: > Library Dependencies: atk, pango, gdk-pixbuf2, gobject-introspection, > xorg-libXi, xorg-libXrandr, > xorg-libXcursor, xorg-libXinerama, xorg-libXdamage, > xorg-libXcomposite, xorg-libXfixes > > So, call this ignorant user error -- how would I make this work without X? See above, but also try %> port info gtk2 +quartz and marvel at the disappeared dependencies ;) > (Turns out it is low priority -- the program that I wanted to install (a GIT > interface) turns out to now be out of date, abandoned, and replaced by a > windows-specific newer program). I use 3 GUI interfaces to git: qgit, KDevelop and Atlassian's SourceTree (not in MacPorts, of course). R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Mono -- does it really need X11?
The standard library includes the GUI components, and I don't think current >> versions make it very easy to split out just the C# compiler and basic >> libraries. > > And I'd guess that C# doesn't make a lot of sense without being able to use > GUI thingies. > > However, Mono uses GTk2, no? And port:gtk2 can be built with +quartz which > doesn't depend on X11 at all from what I can see. Mono's library dependencies: Library Dependencies: gettext, glib2, libiconv, zlib, libgdiplus, xorg-libX11 And, Gtk2 also has: Library Dependencies: atk, pango, gdk-pixbuf2, gobject-introspection, xorg-libXi, xorg-libXrandr, xorg-libXcursor, xorg-libXinerama, xorg-libXdamage, xorg-libXcomposite, xorg-libXfixes So, call this ignorant user error -- how would I make this work without X? (Turns out it is low priority -- the program that I wanted to install (a GIT interface) turns out to now be out of date, abandoned, and replaced by a windows-specific newer program). ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Mono -- does it really need X11?
On Friday February 06 2015 11:33:22 Brandon Allbery wrote: > The standard library includes the GUI components, and I don't think current > versions make it very easy to split out just the C# compiler and basic > libraries. And I'd guess that C# doesn't make a lot of sense without being able to use GUI thingies. However, Mono uses GTk2, no? And port:gtk2 can be built with +quartz which doesn't depend on X11 at all from what I can see. However, gtk2+quartz and gtk2+x11 are currently incompatible, but that's probably not an issue for someone who apparently doesn't have any X11 ports installed at all. R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Mono -- does it really need X11?
On Fri, Feb 6, 2015 at 11:31 AM, Michael wrote: > I'm trying to install a program that needs mono, because it's written for > C#. > So, I try to install mono from macports. > ... and it wants to pull in all of X11? Does C# really require X11? > The standard library includes the GUI components, and I don't think current versions make it very easy to split out just the C# compiler and basic libraries. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Mono -- does it really need X11?
I'm trying to install a program that needs mono, because it's written for C#. So, I try to install mono from macports. ... and it wants to pull in all of X11? Does C# really require X11? --- Entertaining minecraft videos http://YouTube.com/keybounce ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
