Re: libspiro soname bump
On Tue, Feb 3, 2015 at 12:41 AM, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Tue, Feb 03, 2015 at 05:33:40AM +0100, Kevin Kofler wrote: Kevin Fenzi wrote: Just a heads up that I am building a libspiro update in rawhide (only) that has a soname bump in it. The only thing in Fedora that uses libspiro is fontforge and I intend to rebuild that against it as well. Is it really worth announcing the soname bump in such a case? A library only used by one application can effectively be treated as private, especially if you're taking care of the rebuild. (I'm pointing this out because this isn't the first soname bump of this kind being announced.) While you make a point, I prefer to see announce for every soname bump (including those with very little dependency) than taking the risk of missing one (which of course would be an important one). I concur, speaking not only as someone who's missed dependencies before and the announcement helped me avoid breakage, but as someone who sometimes needs to run make clean ; make on personal projects and/or rebuild personal RPMs in these cases. My 2cts, Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- http://cecinestpasunefromage.wordpress.com/ in your fear, seek only peace in your fear, seek only love -d. bowie -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: libspiro soname bump
On Tue, Feb 03, 2015 at 05:33:40AM +0100, Kevin Kofler wrote: Kevin Fenzi wrote: Just a heads up that I am building a libspiro update in rawhide (only) that has a soname bump in it. The only thing in Fedora that uses libspiro is fontforge and I intend to rebuild that against it as well. Is it really worth announcing the soname bump in such a case? A library only used by one application can effectively be treated as private, especially if you're taking care of the rebuild. (I'm pointing this out because this isn't the first soname bump of this kind being announced.) While you make a point, I prefer to see announce for every soname bump (including those with very little dependency) than taking the risk of missing one (which of course would be an important one). My 2cts, Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: libspiro soname bump
Kevin Fenzi wrote: Just a heads up that I am building a libspiro update in rawhide (only) that has a soname bump in it. The only thing in Fedora that uses libspiro is fontforge and I intend to rebuild that against it as well. Is it really worth announcing the soname bump in such a case? A library only used by one application can effectively be treated as private, especially if you're taking care of the rebuild. (I'm pointing this out because this isn't the first soname bump of this kind being announced.) Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
libspiro soname bump
Greetings. Just a heads up that I am building a libspiro update in rawhide (only) that has a soname bump in it. The only thing in Fedora that uses libspiro is fontforge and I intend to rebuild that against it as well. kevin pgpXrn7Dppkve.pgp Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
