On Tue, 2008-04-08 at 11:28 +0200, Salvatore Ansani wrote: > 10x for answer Neil, > I understand what you told but I mean building only a package and not a > library. > > For example, package lastfm depends on libqt4. > If I use kde 4.0.2 environment my qt4 version is 4.3.x. > When I upgrade to KDE 4.0.6x my qt4 version become 4.4.x so lastfm package > breaks and need to be deleted. > > If I recompile lastfm from sources on new libqt4.4-x environment all was ok > and my new lastfm .deb package now correctly depends on libqtcore4 (>= > 4.4.0~beta1). You build against whatever is the current version of the library in unstable and upload that build to unstable - ensuring that it depends on the right version. Then it waits in unstable until the library migrates into testing and it follows. > How I can handle this ??? I can create a .deb package named > lastfm_x.x.x+qt4.4 or something like that ??? NO. You don't rename the package, you just create a new version string. 1.2.3 becomes 1.2.4 etc. If you want to make it a pre-release in experimental, you can do a range of version strings, people have different preferences. I used 0.5.9+0.6.0pre1 for that last one I did. Current unstable at the time had 0.5.6 (IIRC) and 0.6.0 was against a SONAME bump so went into experimental until the library itself was available in unstable. Your package MUST be able to build against unstable or it will get a FTBFS bug from the autobuilders. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
signature.asc
Description: This is a digitally signed message part