<vouivre>
at the end of the compilation of a package if I see
<vouivre>
+libX11
<vouivre>
in the step
<vouivre>
-> libXmu Checking for missing dependencies
<vouivre>
that means the dependency is missing
<vouivre>
right ?
<vouivre>
second question
<vouivre>
if a package needs cairo and gtk+3, for now my reasoning was: gtk+3 is enough.
<vouivre>
But I need to add cairo, because gtk+3 can drop cairo in the future. But my package still needs it.
<vouivre>
in this case, it will probably never happened, but for other packages, something similar could happen.
<vouivre>
also right ?
<vouivre>
ok, answer to my first question is yes
<vouivre>
I just need a confirmation for my second reasoning
<riteo>
vouivre: wrt. dep checking yeah I'm pretty sure when you see a `depends` diff it means that it detected a dependency you didn't specify
<riteo>
note that some software looks at what you have installed and enables some optional features, so until some form of sandboxing or chroot is implemented it's bound to never be perfect for all software and all setups
<riteo>
oh oops just noticed you answered your first question
<riteo>
yeah that's a common occurrence in general, it's called a transitive dependency I think. Basically, just look at your software and see whether you think it "logically" depends on gtk+3 or if it also explicitly uses cairo
<riteo>
like, if you have an ffmpeg-based tool, you wouldn't want to depend also on libopus, as that's irrelevant for the tool itself, as it only "thinks" in ffmpeg terms
<riteo>
(and most importantly only uses its interfaces)
<riteo>
it's a bit like with C/C++ headers
<riteo>
hope that went across
<riteo>
feel free to ask further clarifications :D
lanodan has quit [Ping timeout: 256 seconds]
<vouivre>
riteo: thank you! I understand better now. That's the good new....
<vouivre>
... the bad new is: in how many packages some dependencies are missing.....