Hi, > > better left that way if I don't want to have reports from people about > > incompatibilities with thatX or thatY version of something installed > > when installing avifile. > > I just don't want to force people into rebuilding Qt every time they > > want to install avifile. > > I don't get that logic. By compiling against the latest snapshot of a > testing rpm you want to avoid that people have to rebuild Qt every time they > install a new avifile ??
Rebuilding != installing. > Usually things are backward-compatible only, so you need to compile against > the oldest version still supported in order to make it work automatically > for everyone. Compiling against the newest packages forces _everybody_ to > update _everything_ in order to install your package. Rebuilding != installing. > And by using a gcc 3.1 compiler you even require people to reinstall all C++ > applications, patch glibc by hand with a patch and recompile it as well. Rebuilding != installing. Rebuilding involves complete or partial _recompile_ of some package and _THAT_ I _DO_ want to avoid. > Great dependencies! You got me all wrong. I constantly _DO_ mention that that is Rawhide distro and my goal is that everything else _but_ avifile can be found on rawhide.redhat.com ! And guess what, you _don't_ _have_ to have gccX.X to install avifile from packages that I provide. If some package is required you just wget it and rpm -U it and voala, no configure/make process involved. > Dirk ps yes, I was once running slackware distro, we kept saying that we're 'on slack' :) because the process of ftp/compile/install many times involved a lot of headaches. pps take care, I'm trying to help here -- FUBared. -------------------- H T h i n e t - - W e b M a i l -------------------- Ova poruka poslana je upotrebom HThinet WebMail usluge. https://webmail.hinet.hr _______________________________________________ Avifile mailing list [EMAIL PROTECTED] http://prak.org/mailman/listinfo/avifile
