On Thu, Feb 18, 2016 at 12:24 PM, Paul Eggleton <[email protected]> wrote: > Hi Martin, > > On Thu, 18 Feb 2016 20:39:08 Martin Jansa wrote: >> IIRC this will rename the resulting package (because there will be only one >> shared library now). >> >> that will probably break on device upgrade-path >> >> I'm not sure if someone still cares about upgrade-paths.. there are too >> many issues going in unnoticed. > > The only way we're going to fix that is if we have some automated mechanism > for > picking up on such problems. We have some of the building blocks but so far > nobody has stepped up to write something more complete that can warn us when > such a change has occurred.
Aside from automated detection of such problems, what's the best fix in this particular case? 1) Use LEAD_SONAME to force renaming, even in the case when the libsoup-2.4 package contains both shared libs. 2) Split libsoup-gnome-2.4 into it's own package, so that both libsoup-2.4 and libsoup-gnome-2.4 get renamed. 3) Use DEBIAN_NOAUTONAME to prevent renaming, even when the libsoup-2.4 package only contains one shared lib. 4) Drop the gnome PACKAGECONFIG option so that people can't mess with it (in combination with one of the above). ? > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
