Le 07-10-09 à 02:39, N_Ox a écrit :
Le 9 oct. 07 à 03:30, Randall Wood a écrit :
A couple of notes on this port:
This big dependency chain was introduced because of a note that gtk-engines2 broke if it was installed on a clean machine (ie one that did not have GNOME installed on it first).
After the gettext upgrade fiasco, where I was maintaining some ports (port A) where the dependency chain was A => B => C => D => E => gettext, but all ports A-E were linked to it by E's requirement, only E had the explicit dependency and so A-D had to be manually reinstalled. It seems smart to be overly explicit about dependencies in these cases.
That said, there may be some overkill here, but I'm not sure how to determine what is and what isn't overkill.
I usually go through the configure.(ac|in) file and grep sources around for #include preprocessor directives to figure out which are real dependencies and which aren't.
Well, if it can help with port upgrade, this is definitely worth it. yves