Am 01.10.2012 03:03, schrieb James Buren: [..]
> No package change may be done directly in current if it would result in ABI > breakage in a package residing in > a main group (not suffixed with -extra). To check if the ABI is broken, run > fpmdiff on the old FPM vs the new FPM. > The ABI is broken when the first number is changed. Below are some examples > of where the ABI is broken and > when it is not. > > > Examples: > > libfoo.so.1.0.0 -> libfoo.so.1.1.0 (ABI is not broken) > libfoo.so.1.0.0 -> libfoo.so.1.0.1 (ABI is not broken) > libfoo.so.1.0.0 -> libfoo.so.2.0.0 (ABI is broken) You can't be sure those first two lines will not result in ABI breakage. To bump major version is convenient but not all lib developers will do it ;) I'm fine with using your proposed path and bump every package in WIP that changes major lib versions. But I'm also pretty sure this won't protect from ABI breakages in current. For this to work, though I propose something like "dev roadmaps" (perhaps in tracker?) to check if some other dev is already working on one or another package. Doing WIPs usualy means longer times until packages hit current and possibly more time wasted on bumping the same packages by different devs, or one dev bumping the dep Nr.1 and another at the same time Nr. 2. resulting in conflicts (and possibly high waste of buildtime ;) Greetings DeX _______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
