curious dependency issues

[David Strubbe]

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 <egall at 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 <dstrubbe at 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 <pixilla at macports.org>wrote:
>>
>>> On Apr 7, 2014, at 9:12 AM, David Strubbe <dstrubbe at 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 at lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20140407/4e6cce2f/attachment-0001.html>