It'd be a dilemma, upstream didn't do that, while downstream can do
that and then the commit will be objected by the others.
See the example of json-c[1].
[1]---https://lists.fedoraproject.org/pipermail/devel/2014-July/201320.html
--
Yours sincerely,
Christopher Meng
http://cicku.me
--
devel
Sébastien Willmann wrote:
> I going to update jsoncpp to the latest github commit in rawhide. This is
> an ABI break with no soname change.
Why is there no soname change? (ie, there probably should be)
-- Rex
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/
- Original Message -
> I going to update jsoncpp to the latest github commit in rawhide. This is an
> ABI
> break with no soname change.
That’s rather risky, any of the users could break without any RPM dependency
failure. Could you at least file a bug against every package using jsoncp
Hello,
I going to update jsoncpp to the latest github commit in rawhide. This is an ABI
break with no soname change.
See https://bugzilla.redhat.com/show_bug.cgi?id=1143774
pgpZWCqBPzpR6.pgp
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproj
