Bug 819777

Summary:	dev-cpp/yaml-cpp 0.7.0-r1 should be in another slot
Product:	Gentoo Linux	Reporter:	Szef <gena.kazachek>
Component:	Current packages	Assignee:	Alexey <alexey+gentoo>
Status:	RESOLVED CANTFIX
Severity:	normal	CC:	alexey+gentoo, ionen, proxy-maint
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Szef 2021-10-23 17:07:53 UTC

dev-cpp/yaml-cpp from 0.7.0 is not backward compatible with 0.6.3, so it should go to another slot

Reproducible: Always

Steps to Reproduce:
Actually my working project failed to compile after upgrade to 0.7.0-r1, as lib's classes signatures changed.
Not sure, if I can explain any better.

Comment 1 Szef 2021-10-23 17:27:07 UTC

https://github.com/jbeder/yaml-cpp/compare/yaml-cpp-0.6.3...yaml-cpp-0.7.0

Comment 2 Szef 2021-10-23 17:28:16 UTC

include/yaml-cpp/exceptions

Comment 3 Ionen Wolkens gentoo-dev

2021-10-23 20:19:40 UTC

When possible, typically it's better to try to avoid slotting and instead ensure packages are compatible with the new one so we can move on (especially on 0.x.x semver packages without a stable API, we'll just be accumulating slots without real support).

Any chances to just migrate your project instead? Same would go for any ::gentoo packages failing with this.

Comment 4 Szef 2021-10-23 21:53:43 UTC

My project will be fine, I fixed it already. 
If there is no gentoo packages that rely on changed part of the API, and it is not worth slotting, then bug can be closed.

Comment 5 Alexey 2021-10-24 11:41:46 UTC

Slots are for cases when both versions can be installed simultaneously. This package installs yaml-cpp.pc, which presumably clients use via pkg-config. The both packages can't install the same .pc file, so at least one of these types of clients will be broken. Unless we go the python eclasses way, but no.