Le 21 avr. 08 à 17:51, Alexander Hansen a écrit : > This is a new pet peeve for me, especially when validating packages > from > the tracker. Typically it happens due to a BuildDepend on doxygen, > which in turn depends on TeX. And I don't know how often that is > actually necessary: some packages check for doxygen and graphviz, > but a > normal build doesn't _use_ them. > > I don't have time just yet, but at some point it might be worth > auditing > packages to see how many of these BuildDepends are spurious.
Could you help me with one case, please? I used the system-texlive.info suggested previously on this thread, and the package installs successfully (I have TeXLive 2007 installed). But after that, I tried to install kdelibs3-unified. Among its dependencies, it pulls tetex-base and tetex-texmf with it. I edited system-texlive.info, added those packages to the "provides" section and reinstalled it. Fink reports tetex-base as a "provided" package, so it works. But kdelibs3 still pulls the real tetex-base package as a dependency... What am I missing? Why can't kdelibs3 be happy with the provided tetex-base? Thanks in advance, -- Thibaut Cousin http://www.thibaut-cousin.net ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
