https://bugzilla.redhat.com/show_bug.cgi?id=1215342
--- Comment #4 from Kalev Lember <[email protected]> --- Thanks Zbigniew! I don't know of any explicitly written down guidelines and Toshio's post is probably the best we have. The rule of thumb that I've always tried to follow is to use the compat- prefix when I need ABI compatibility, but don't want newly built programs to be able to link with the old ABI. This is the case here. If I'd additionally want API compatibility and to be able to link against the library, then I wouldn't use compat- and would go with a regular parallel installable libfoo1{,-devel}, libfoo2{,-devel} naming scheme instead. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/package-review
