rdepof:wine-devel +x11 +universal fails on installing xattr
Gijs Vermeulen
gijsvrm at gmail.com
Mon Sep 10 01:47:24 UTC 2018
Hi,
Thank you both for the answers.
In the end I ended up using Ryan's command that excludes xattr and that
worked perfectly.
Thanks again!
Regards,
Gijs
Op za 8 sep. 2018 om 02:54 schreef Ken Cunningham <
ken.cunningham.webuse at gmail.com>:
>
> On 2018-09-07, at 5:33 PM, Ryan Schmidt wrote:
>
>
> > I understand that you are saying that, but I'm not convinced that's
> desirable behavior.
> >
> > What criteria do you propose to use to exclude the dependency? The
> dependency is written "bin:xattr:xattr". Do you propose to exclude all bin
> (and lib?) dependencies? Or do you only propose to exclude bin (and lib?)
> dependencies that are already satisfied by the specified program (or
> library?)? And if so, do you exclude the dependency regardless of how the
> dependency was satisfied, or only if the dependency was satisfied by a file
> outside of MacPorts? And if the latter, where in MacPorts base should that
> determination be made? (As far as I know, MacPorts base doesn't currently
> care where the file that satisfies a bin (or lib) dependency is located.)
> >
>
> Whew -- might take me a while to digest all that.
>
> In essence, I think most users would expect that:
>
> port echo rdepof:wine-devel +x11 +universal
>
> would lead to more or less the same dependencies being listed as would be
> installed if you instead did:
>
> port install wine-devel +x11 +universal
>
> But if that is not desirable behaviour for some reason, OK. I actually
> don't use rdepof.
>
> Best,
>
> Ken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20180910/50e78978/attachment.html>
More information about the macports-users
mailing list