On Sun, Nov 13, 2005 at 04:27:27PM +0100, sebastien marbrier wrote: > Le Dimanche 13 Novembre 2005 15:40, Ming Hua a écrit : > > > If you mean the backported scim 1.4.1-1 packages for sarge, I would > > suggest you consider the C++ ABI issue. The package 1.4.1-1 in sid > > builds binary package libscim8, which uses the GCC 4.0 new ABI. If you > > backport it to sarge, the right thing to do is to build a library > > package of different name, and have it conflict with libscim8. If you > > don't take care of the C++ ABI issue, I think there may be many strange > > and hard-to-dectect error happening when users mix scim packages built > > in different environments. > > According to the instructions from www.backports.org, I have changed > the name of the source directory from scim-1.4.1-1 to > scim-1.4.1-backports.org.1 > After the construction of the package, I obtain > libscim8_1.4.1-backports.org.1_i386.deb > Is it that you recommended ?
No, I am talking about rename the *package* name, like from libscim8 to libscim8c102 (altough you need to change the version as well). > I can't see any libscim8 in sarge so I don't see > how I can make a conflict. I'm talking about conflicting with libscim8 in unstable. See the announcement in debian-devel-announce mailing list (around July or August) for the reason why this is necessary. Ming 2005.11.13 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
