Différences entre versions de « Backport SDL ttf »
imported>SylvainBeucler m (Nouvelle page : We use the same technique than in Backport FreeType. apt-src install libsdl-ttf2.0-0 cd sdl-ttf2.0-2.0.9/ dch -i <code>changelog</code> entry: sdl-ttf2.0 (2.0.9-1~bpo40+1) ...) |
imported>SylvainBeucler m (mention pbuilder) |
||
Ligne 17 : | Ligne 17 : | ||
Granted, using SDL_ttf alone may not be very useful in this particular case, but that's not the backports philosophy, and you never know what users really need. | Granted, using SDL_ttf alone may not be very useful in this particular case, but that's not the backports philosophy, and you never know what users really need. | ||
+ | When building a single package (i.e. without depending on other backported packages) it's easier to use pbuilder, cf. | ||
+ | [[Backport_FreeType#Cleaner_compilation]]. | ||
TODO: I think we now should include all the changelog entries between the stable version and the backported one in the <code>.changes</code> file. debuild option? | TODO: I think we now should include all the changelog entries between the stable version and the backported one in the <code>.changes</code> file. debuild option? |
Version actuelle datée du 28 mars 2008 à 17:15
We use the same technique than in Backport FreeType.
apt-src install libsdl-ttf2.0-0 cd sdl-ttf2.0-2.0.9/ dch -i
changelog
entry:
sdl-ttf2.0 (2.0.9-1~bpo40+1) etch-backports; urgency=low * Rebuild for Debian Backports <http://www.backports.org/> (new version fixes rendering bugs) -- Sylvain Beucler <beuc@beuc.net> Tue, 11 Dec 2007 01:18:53 +0100
Warning: if you backport SDL_ttf you're almost certainly already have backported FreeType (since Etch's version makes SDL_ttf crash). However you need compile sdl-ttf2.0 _without_ your libfreetype6 backport installed. Otherwise shlibs will automatically detect it and add a dependency to "libfreetype6 (>= 2.3.5)" (instead of Etch's 2.2.1-5), and people won't be able to use your SDL_ttf backport alone.
Granted, using SDL_ttf alone may not be very useful in this particular case, but that's not the backports philosophy, and you never know what users really need.
When building a single package (i.e. without depending on other backported packages) it's easier to use pbuilder, cf. Backport_FreeType#Cleaner_compilation.
TODO: I think we now should include all the changelog entries between the stable version and the backported one in the .changes
file. debuild option?