On Wed, 18 Mar 2009 19:13:03 +0900 Charles Plessy <plessy@debian.org> wrote: > Le Wed, Mar 18, 2009 at 07:25:40AM +0000, Neil Williams a écrit : > > > > Maintainers will be creating TDebs in Squeeze+1, using debian/rules, > > using debhelper calls and uploading TDebs each time they would > > currently upload any package that contains /usr/share/locale/LC_*/ etc. > > Those TDebs are, effectively, +t0 - only updates by translators start > > the +t1 sequence. > > > > Maintainer uploads: > > foo_1.2.3-4_amd64.deb > > foo-tdeb_1.2.3-4_all.tdeb > > foo-bar_1.2.3-4_amd64.deb > > foo_1.2.3-4.diff.gz > > foo_1.2.3.orig.tar.gz > > foo_1.2.3-4.dsc > > foo_1.2.3-4_amd64.changes > > Hi Neil, > > how do you coordinate your action with the project of using the source format > '3.0 (quilt)' by default in Squeeze +1? Why should 3.0 be any more difficult than 1.0 or anything that follows? (Not that I have any particular desire to use 3.0 or quilt myself.) 3.0 has to deal with incorporating patches and changes from the BTS, so +t1.diff.gz is no different. In Squeeze+1, the changes are restricted to debian/po or po/ for native Debian packages so there is no need to do anything with 3.0 until Squeeze+2. What matters is that the maintainer gets the +t1.diff.gz and applies it onto the source package prior to the next upload. It's no different to how the same maintainer would handle a patch or new translations file sent to the BTS. I'm quite sure various tools and scriptage will be devised to help with different workflow patterns before Squeeze+2. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgp8tqOxkRDhr.pgp
Description: PGP signature