Jean-François Mertens wrote: [] > But if moving a file from unstable to stable, I've to be sure > that all its deps and builddeps (and hence recursively so..) > are in stable, and are IDENTICAL, or else I have to make > sure that exactly the same deb and the same functionality > obtains
Just a remork on this point: While it is official Fink policy that debs with identical names should be identical, this remains largely a dream. In general, debs built against unstable will not run on stable, even if they come from the same package description, and debs built on recent checkouts of Fink will not run on earlier versions. The main reason is library compatibility. If we would seriously insist on requiring a certain fixed compatibility_version for all dylibs linked into a package, updating shlibs packages would become completely impossible. This is also one of the reasons why making bindists is so difficult. You have to be sure that you build against the lowest common denominator of all current packages. If the debs were always the same, this would be much easier and anyone could submit debs for the bindist. With fftw3 this is even worse: If you build it on a G5, you cannot run it on a G4, which is major hassle for private unstable bindist servers. -- Martin ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
