Hello, I'm new to macports and experimenting with it. To that end, I was wondering if there is a simple way to list all dependencies recursively in macports. For example, the standard 'macports deps foo' command does not list the deps of the deps. I found a perl script that does something similar in nature here: http:// lists.macosforge.org/pipermail/macports-users/2007-April/002481.html But, I mean, who wants to run perl scripts instead of a port command? :) Also, the portfile for grace has the following dependency line: depends_lib lib:libX11.6:XFree86 \ X11 for Leopard provide X11R7 (instead of 6) and is based on xorg, not XFree86. But, I know that macports grace works in Leopard. So I'm wondering, how exactly is that line parsed? How badly malformed would it have to be, before macports tries to compile XFree86 itself or just refuses to install? thanks for reading, Brian
Also, the portfile for grace has the following dependency line: depends_lib lib:libX11.6:XFree86 \
X11 for Leopard provide X11R7 (instead of 6) and is based on xorg, not XFree86. But, I know that macports grace works in Leopard. So I'm wondering, how exactly is that line parsed? How badly malformed would it have to be, before macports tries to compile XFree86 itself or just refuses to install?
Leopard's X11 still uses libX11.6, even though being /usr/X11/ and X.org based --anders
On Dec 20, 2007, at 4:31 PM, Anders F Björklund wrote:
Also, the portfile for grace has the following dependency line: depends_lib lib:libX11.6:XFree86 \
X11 for Leopard provide X11R7 (instead of 6) and is based on xorg, not XFree86. But, I know that macports grace works in Leopard. So I'm wondering, how exactly is that line parsed? How badly malformed would it have to be, before macports tries to compile XFree86 itself or just refuses to install?
Leopard's X11 still uses libX11.6, even though being /usr/X11/ and X.org based
I guess it may still be there in symlink or in full, but I am just going on the X11R7 info as provided at: http://trac.macosforge.org/projects/xquartz/wiki/DeveloperInfo and http://developer.apple.com/opensource/tools/X11.html still curious about my questions, though :) thanks, -Brian
On Dec 20, 2007, at 15:35, Brian Barnes wrote:
I'm new to macports and experimenting with it. To that end, I was wondering if there is a simple way to list all dependencies recursively in macports. For example, the standard 'macports deps foo' command does not list the deps of the deps. I found a perl script that does something similar in nature here: http:// lists.macosforge.org/pipermail/macports-users/2007-April/002481.html
But, I mean, who wants to run perl scripts instead of a port command? :)
I have a PHP script to do the same, and generate a graphviz graph out of it. There's no built-in command in port.
Also, the portfile for grace has the following dependency line: depends_lib lib:libX11.6:XFree86 \
X11 for Leopard provide X11R7 (instead of 6) and is based on xorg, not XFree86. But, I know that macports grace works in Leopard. So I'm wondering, how exactly is that line parsed? How badly malformed would it have to be, before macports tries to compile XFree86 itself or just refuses to install?
The line means "This port depends on the library libX11.6, and if that library is not found, install the XFree86 port." Apple's X11, installed by default on Leopard and listed in the MacPorts system requirements, provides libX11.6, so the XFree86 port is not installed.
On Dec 21, 2007, at 02:33, Ryan Schmidt wrote:
On Dec 20, 2007, at 15:35, Brian Barnes wrote:
I'm new to macports and experimenting with it. To that end, I was wondering if there is a simple way to list all dependencies recursively in macports. For example, the standard 'macports deps foo' command does not list the deps of the deps. I found a perl script that does something similar in nature here: http:// lists.macosforge.org/pipermail/macports-users/2007-April/002481.html
But, I mean, who wants to run perl scripts instead of a port command? :)
I have a PHP script to do the same, and generate a graphviz graph out of it. There's no built-in command in port.
Though I do think it would be cool if there were a port command which would compute the dependencies recursively and output them as a textual tree (with indented lines, say). Also, I'd like a second port command which would output the dependency graph in graphviz dot format. And maybe even a way to have graphviz open that into a window so you could see it. Alas, that's not here yet, and there are probably more important things we should be working on.
Citando Ryan Schmidt :
On Dec 21, 2007, at 02:33, Ryan Schmidt wrote:
On Dec 20, 2007, at 15:35, Brian Barnes wrote:
I'm new to macports and experimenting with it. To that end, I was wondering if there is a simple way to list all dependencies recursively in macports. For example, the standard 'macports deps foo' command does not list the deps of the deps. I found a perl script that does something similar in nature here: http://lists.macosforge.org/pipermail/macports-users/2007-April/002481.html
But, I mean, who wants to run perl scripts instead of a port command? :)
I have a PHP script to do the same, and generate a graphviz graph out of it. There's no built-in command in port.
Though I do think it would be cool if there were a port command which would compute the dependencies recursively and output them as a textual tree (with indented lines, say).
Also, I'd like a second port command which would output the dependency graph in graphviz dot format. And maybe even a way to have graphviz open that into a window so you could see it. Alas, that's not here yet, and there are probably more important things we should be working on.
Maybe you could make a portfile for it (which lets you use your preferred language to code it) à la pkgdepgraph which is just another package for pkgsrc and does this sort of things. It is not something every user needs but would be pretty cool in a number of situations, so it may not necessarily be in base. Emmanuel
participants (4)
-
Anders F Björklund
-
Brian Barnes
-
Emmanuel Hainry
-
Ryan Schmidt