On Sep 3, 2006, at 4:34 PM, Alexander Hansen wrote: > On 9/3/06, Peter Dyballa <[EMAIL PROTECTED]> wrote: >> Hello! >> >> When trying an update-all after a selfupdate, this failed because >> libjasper1 had to be removed – and it is too hard to ask my >> permission? Even the package gets re-installed afterwards? > > It's a BuildConflict. Fink tries to remove the package that's causing > the conflict, and it doesn't ask your permission in this case because > it's removing a package that nothing depends on (such packages usually > are development headers and the like).
Hi, I had some email problems (our University is upgrading their entire email infrastructure this weekend) but sent some more thoughts off- list to Alexander. Here is what I'd suggest: If I add the configure flag "--without-jasper" in ghostscript.info, there is no build conflict with libjasper1. I tried to find out specifically what would be different if I give either no configure flags or specify the flag "--with-jasper" (as suggested by configure --help); but I can't find any added jpeg capabilities that this provides, compared to what ghostscript 8.51 already offers based on libjpeg (on which it BuildDepends). So I think the best fix is to submit a new ghostscript.info file which has the configure flag --without-jasper and then no longer needs a BuildConflict entry. Jens ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
