[97320] trunk/dports/graphics/librsvg/Portfile

[Ryan Schmidt]

On Sep 3, 2012, at 15:29, Joshua Root wrote:

>> I remember some rule of thumb about not listing as direct dependency
>> something that is known to be a recursive dependency, but actually
>> couldn't find anything relevant in guide or wiki. Is there such a
>> guideline at all?
> 
> It's a rule of thumb, sure, because otherwise many dependency lists
> would be huge. It shouldn't be followed if there's a good reason not to
> in a particular case.

And are we in agreement that linking with a library is a good reason not to omit the dependency? And that therefore we should go back and add the libpng dependency to every port that links with it? Because at the moment that is what I plan to do as I go through and fix various libpng 1.5 breakages. I'm conflicted about adding the dependency, but it seems the best solution we have at this time, given that we do not yet have the ideal automated solution you alluded to below:


>>> Of course, ideally all cases of breakage from library major version
>>> changes would be autodetected, and adding such explicit deps would be
>>> unnecessary.
>> 
>> The archives we distribute never get rebuilt in this case: a user will download and install them, then be whisked away to reinstall/rebuild.
> 
> Yes, I didn't say we had achieved this ideal.