Niels Breet on 01/18/2010 03:08 PM wrote:
Can we, like with the opt problem, come to a solution with community power[tm]?
An SONAME change during a distribution version's lifetime is quite nasty. Most, if not all, distributions frown upon such a thing. I'm surprised that this was done, given the locked down state of some Brainstorm ideas. I realize that sometimes it is unavoidable, but a e-mail to the maemo-developers list would have been helpful. More communication the better. :)
The proper way to handle it would be option 3. The Maemo build system should be able to perform "Broken Dependency" checks daily (or upon your request) to insure a stateful system. An e-mail[1] to maemo-developers (or the appropriate list) should be sent that lists the broken packages. If there are packages that were built against an older SONAME, a Maemo or Nokia member should rebuild those packages and file bugs with the project if a rebuild fails. The package release number should be incremented and a changelog entry that defines "Rebuild for $LIBRARY_NAME change" should be added.
[1] http://lists.fedoraproject.org/pipermail/test/2010-January/087997.html _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
