Re: curious dependency issues
Well I really think this needs to be documented more clearly. The examples in the guide do not mention it is a regex rather than the exact name of a port, and that is the only documentation I have seen on it. David On Mon, Apr 7, 2014 at 8:46 PM, Ryan Schmidt ryandes...@macports.orgwrote: On Apr 7, 2014, at 17:14, David Strubbe wrote: Ok, I think I see what is going on here: apparently port installed depends:XXX returns all ports depending on port XXX -- OR a port that contains the string XXX. It's a regular expression search. So if you want the ports that depend on gcr, you could use: $ port echo depends:':gcr($|\s)' empathy epiphany evolution-data-server gnome-keyring gnome-online-accounts gnome3-core libgdata seahorse $ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
curious dependency issues
Hi all, I found two strange things in using 'port installed depends:'. The 'gcr' port appears to depend on itself, and gconf and gtk3 appear to depend on each other. Does this make sense? Is it a bug in base or the Portfiles? David $ port installed depends:gcr The following ports are currently installed: gcr @3.10.1_0 gcr @3.10.1_1 gcr @3.10.1_2 (active) ... $ port installed depends:gconf | grep gtk ... gtk2 @2.24.23_0+no_x11+quartz (active) gtk3 @3.8.2_0+x11 ... gtk3 @3.12.0_0+x11 (active) $ port installed depends:gtk3 ... gconf @2.32.4_2+quartz gconf @2.32.4_3+quartz (active) gcr @3.10.1_0 gcr @3.10.1_1 gcr @3.10.1_2 (active) ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: curious dependency issues
On Apr 7, 2014, at 9:12 AM, David Strubbe dstru...@gmail.com wrote: Hi all, I found two strange things in using 'port installed depends:'. The 'gcr' port appears to depend on itself, and gconf and gtk3 appear to depend on each other. Does this make sense? Is it a bug in base or the Portfiles? I don't know if depends: is a bug but it is not documented in man port whereas depof: is: port installed depof:gcr Regards, Bradley Giesbrecht (pixilla) ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: curious dependency issues
Hm, I guess I got depends: from suggestions in messages on this list. Using port installed depof:gcr gcr is not listed, so that is more reasonable. depof:gtk3 does not list gconf, and depof:gconf does list gtk3. So it seems that depends: is buggy. Maybe it should be removed if it has been supplanted by depof:. David On Mon, Apr 7, 2014 at 2:03 PM, Bradley Giesbrecht pixi...@macports.orgwrote: On Apr 7, 2014, at 9:12 AM, David Strubbe dstru...@gmail.com wrote: Hi all, I found two strange things in using 'port installed depends:'. The 'gcr' port appears to depend on itself, and gconf and gtk3 appear to depend on each other. Does this make sense? Is it a bug in base or the Portfiles? I don't know if depends: is a bug but it is not documented in man port whereas depof: is: port installed depof:gcr Regards, Bradley Giesbrecht (pixilla) ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: curious dependency issues
I was under the impression that the depends: pseudo-portname and the depof: portname were two separate things... On Mon, Apr 7, 2014 at 2:19 PM, David Strubbe dstru...@gmail.com wrote: Hm, I guess I got depends: from suggestions in messages on this list. Using port installed depof:gcr gcr is not listed, so that is more reasonable. depof:gtk3 does not list gconf, and depof:gconf does list gtk3. So it seems that depends: is buggy. Maybe it should be removed if it has been supplanted by depof:. David On Mon, Apr 7, 2014 at 2:03 PM, Bradley Giesbrecht pixi...@macports.orgwrote: On Apr 7, 2014, at 9:12 AM, David Strubbe dstru...@gmail.com wrote: Hi all, I found two strange things in using 'port installed depends:'. The 'gcr' port appears to depend on itself, and gconf and gtk3 appear to depend on each other. Does this make sense? Is it a bug in base or the Portfiles? I don't know if depends: is a bug but it is not documented in man port whereas depof: is: port installed depof:gcr Regards, Bradley Giesbrecht (pixilla) ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: curious dependency issues
Indeed, evidently depends: does some strange things which depof: does not. Though man port does not define depends:, it is recommended here: https://guide.macports.org/#using.common-tasks.finddepending By contrast, depof: does not seem to appear in the guide. David On Mon, Apr 7, 2014 at 2:46 PM, Eric Gallager eg...@gwmail.gwu.edu wrote: I was under the impression that the depends: pseudo-portname and the depof: portname were two separate things... On Mon, Apr 7, 2014 at 2:19 PM, David Strubbe dstru...@gmail.com wrote: Hm, I guess I got depends: from suggestions in messages on this list. Using port installed depof:gcr gcr is not listed, so that is more reasonable. depof:gtk3 does not list gconf, and depof:gconf does list gtk3. So it seems that depends: is buggy. Maybe it should be removed if it has been supplanted by depof:. David On Mon, Apr 7, 2014 at 2:03 PM, Bradley Giesbrecht pixi...@macports.orgwrote: On Apr 7, 2014, at 9:12 AM, David Strubbe dstru...@gmail.com wrote: Hi all, I found two strange things in using 'port installed depends:'. The 'gcr' port appears to depend on itself, and gconf and gtk3 appear to depend on each other. Does this make sense? Is it a bug in base or the Portfiles? I don't know if depends: is a bug but it is not documented in man port whereas depof: is: port installed depof:gcr Regards, Bradley Giesbrecht (pixilla) ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: curious dependency issues
Ok, I think I see what is going on here: apparently port installed depends:XXX returns all ports depending on port XXX -- OR a port that contains the string XXX. This seems like a bug, and gives very misleading information. * gcr appears to depend on itself because it depends on libgcrypt. * gtk3 appears to depend on gconf because it depends on pkgconfig. * If I write port installed depends:a (despite there being no port called a) I get 8636 ports returned. * The list returned from port installed depends:libxc includes the dependencies not only of libxc but also of the entirely unrelated xorg-libxcb, xorg-libXcomposite, and xorg-libXcursor. David On Mon, Apr 7, 2014 at 6:01 PM, David Strubbe dstru...@gmail.com wrote: Indeed, evidently depends: does some strange things which depof: does not. Though man port does not define depends:, it is recommended here: https://guide.macports.org/#using.common-tasks.finddepending By contrast, depof: does not seem to appear in the guide. David On Mon, Apr 7, 2014 at 2:46 PM, Eric Gallager eg...@gwmail.gwu.eduwrote: I was under the impression that the depends: pseudo-portname and the depof: portname were two separate things... On Mon, Apr 7, 2014 at 2:19 PM, David Strubbe dstru...@gmail.com wrote: Hm, I guess I got depends: from suggestions in messages on this list. Using port installed depof:gcr gcr is not listed, so that is more reasonable. depof:gtk3 does not list gconf, and depof:gconf does list gtk3. So it seems that depends: is buggy. Maybe it should be removed if it has been supplanted by depof:. David On Mon, Apr 7, 2014 at 2:03 PM, Bradley Giesbrecht pixi...@macports.org wrote: On Apr 7, 2014, at 9:12 AM, David Strubbe dstru...@gmail.com wrote: Hi all, I found two strange things in using 'port installed depends:'. The 'gcr' port appears to depend on itself, and gconf and gtk3 appear to depend on each other. Does this make sense? Is it a bug in base or the Portfiles? I don't know if depends: is a bug but it is not documented in man port whereas depof: is: port installed depof:gcr Regards, Bradley Giesbrecht (pixilla) ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: curious dependency issues
On Apr 7, 2014, at 17:14, David Strubbe wrote: Ok, I think I see what is going on here: apparently port installed depends:XXX returns all ports depending on port XXX -- OR a port that contains the string XXX. It’s a regular expression search. So if you want the ports that depend on gcr, you could use: $ port echo depends:':gcr($|\s)' empathy epiphany evolution-data-server gnome-keyring gnome-online-accounts gnome3-core libgdata seahorse $ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: curious dependency issues
On 2014-4-8 04:03 , Bradley Giesbrecht wrote: On Apr 7, 2014, at 9:12 AM, David Strubbe dstru...@gmail.com wrote: Hi all, I found two strange things in using 'port installed depends:'. The 'gcr' port appears to depend on itself, and gconf and gtk3 appear to depend on each other. Does this make sense? Is it a bug in base or the Portfiles? I don't know if depends: is a bug but it is not documented in man port whereas depof: is: port installed depof:gcr Those do two different things: depof:gcr tells you the ports that gcr depends on, whereas depends:gcr tells you the ports that depend on gcr (or any other port name that matches the regex). - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
