Hi Joshua,
On 14 Apr 2014, at 10:56 , Joshua Root wrote:
> Dependents are precisely those ports that are needed at runtime. We
OK, it’s not inconsistent, I see that now.
Good, have to check on this again, once kdelibs4’s dependency on nepomuk and
thus openssl is gone.
> You maybe want something
On 2014-4-14 05:24 , mk-macpo...@techno.ms wrote:
> On 13 Apr 2014, at 21:12 , Joshua Root wrote:
>> What would this warning say, and where would it go? And have you read
>> the help for port rdeps?
>
> Ah, sorry, now I see that there is indeed an option "--no-build" there.
>
> But still, one co
Hi,
> On 14 Apr 2014, at 01:52 , Ryan Schmidt wrote:
> > By definition, a build dependency isn’t needed at runtime, so you wouldn’t
> > distribute it, so you wouldn’t care about build dependencies’
> > distributability, would you?
>
> Hmmm, you’ve got your point.
> When I was writing those lines
On 14 Apr 2014, at 01:52 , Ryan Schmidt wrote:
> By definition, a build dependency isn’t needed at runtime, so you wouldn’t
> distribute it, so you wouldn’t care about build dependencies’
> distributability, would you?
Hmmm, you’ve got your point.
When I was writing those lines I awaited this k
On Apr 13, 2014, at 14:24, mk-macpo...@techno.ms wrote:
> On 13 Apr 2014, at 21:12 , Joshua Root wrote:
>> What would this warning say, and where would it go? And have you read
>> the help for port rdeps?
>
> Ah, sorry, now I see that there is indeed an option "--no-build" there.
>
> But still,
On 13 Apr 2014, at 21:12 , Joshua Root wrote:
> What would this warning say, and where would it go? And have you read
> the help for port rdeps?
Ah, sorry, now I see that there is indeed an option "--no-build" there.
But still, one could make use of an option like “--with-build” for the
rdepend
On 2014-4-14 02:31 , mk-macpo...@techno.ms wrote:
> On 13 Apr 2014, at 18:01 , Brandon Allbery wrote:
>> Well, this is still highlighting an inconsistency.
> Yes, right you are, otherwise I wouldn’t have stumbled over it.
I don't think it's inconsistent, the information being expressed is just
in
On 13 Apr 2014, at 19:08 , Jeremy Lavergne wrote:
> Using verbose (port -v) might list out the types of dependencies.
The only difference I can see here is that the -v version puts “port:” in front
of the port names…
What am I missing?
—
$ port deps gtk2
Full Name: gtk2 @2.24.23_0+x11
Extract De
Using verbose (port -v) might list out the types of dependencies.
On April 13, 2014 12:01:11 PM EDT, Brandon Allbery wrote:
>On Sun, Apr 13, 2014 at 11:51 AM, wrote:
>
>> On 13 Apr 2014, at 17:46 , Brandon Allbery
>wrote:
>> > Looks like it's because it's a build dependency --- so, while the
>g
On 13 Apr 2014, at 18:01 , Brandon Allbery wrote:
> Well, this is still highlighting an inconsistency.
Yes, right you are, otherwise I wouldn’t have stumbled over it.
> In this case, I think it's between the actual record of dependencies in the
> package registry (produced by actually installing
On Sun, Apr 13, 2014 at 11:51 AM, wrote:
> On 13 Apr 2014, at 17:46 , Brandon Allbery wrote:
> > Looks like it's because it's a build dependency --- so, while the gtk2
> port is what pulled it in, it is not needed at runtime.
> Ahhh, I see.
> Thanks for solving this mystery! :-)
Well, this is
On 13 Apr 2014, at 17:46 , Brandon Allbery wrote:
> Looks like it's because it's a build dependency --- so, while the gtk2 port
> is what pulled it in, it is not needed at runtime.
Ahhh, I see.
Thanks for solving this mystery! :-)
Greets,
Marko
___
mac
On Sun, Apr 13, 2014 at 10:39 AM, wrote:
> But if I let port show me all kmymoney4-devel deps it gets listed:
> —
> $ port rdeps kmymoney4-devel
> ...
> kde4-runtime
> kdelibs4
> soprano
> libiodbc
> gtk2
> gtk-doc
> …
> —
>
> So, the question is, why the
Hi,
port gtk-doc puzzled me just now, since it doesn’t seem to have dependent ports.
—
$ port rdependents gtk-doc
gtk-doc has no dependents.
—
But if I let port show me all kmymoney4-devel deps it gets listed:
—
$ port rdeps kmymoney4-devel
...
kde4-runtime
kdelibs4
soprano
li
14 matches
Mail list logo
