Hello Sebastian, Bugreporters, On Fri, 21 Jul 2017, at 14:58, Sebastian Ramacher wrote: > > On Thu, Jul 20, 2017 at 02:34:42PM +0200, Sebastian Ramacher wrote: > > > > currently there are two versions of libupnp in the archive (libupnp6 and > > > > libupnp-1.8-10). To be able to remove libupnp6 (i.e. the older of the > > > > two) it is necessary to port vlc (and all other rdepends) to > > > > libupnp-1.8. > > > > > > > > The patch below implements this for vlc. With this applied I can still > > > > playback videos with vlc. > > > > > > As long as the adoption to upnp 1.8 requires to add -1.8 everywhere (are > > > we > > > supposed to change it to -1.9 next month with the next upstream > > > release?), this > > > was explicitly NAKed upstream. > > > > Which upstream? vlc I suppose? Do you have a link to the discussion > > handy? > > Yes, vlc upstream. This was over IRC and I don't have logs. But I'm sure > J-B > will repeat it if necessary (CCed)
Sure. Since when releasing a new version of a library requires changing all the includes and all the pkg-config detection? SO names are done to notate API/ABI changes within a library and PKG-CONFIG files are done to show where to find the includes folder and how to link. If you do a moderate breaking change, you change the API, the ABI, and bump the library version name majorly. And people linking against you will need to adapt, when they bump the requirements. This was done for almost every minor C/C++ library, since forever. So, sorry, but this way of renaming the headers folder name and changing the .pc files is completely backward; and sorry, totally not justified, because it's justified for complete rewrites, not for a moderate change. If you want to do that anyway, at least provide the same .pc file name which gives the new includes. Best, -- Jean-Baptiste Kempf - President +33 672 704 734
