Use of the XS-Vcs-bzr (or -git, ...) debian/control field

[Matt Zimmerman]

On Wed, Mar 07, 2007 at 09:35:51PM +0000, Colin Watson wrote:
> On Wed, Mar 07, 2007 at 08:52:20AM -0800, Matt Zimmerman wrote:
> > On Wed, Mar 07, 2007 at 09:59:54AM +0000, Colin Watson wrote:
> > > The main question I have is: what should be done with packages that
> > > already have an XS-Vcs-* field from Debian? For example, the installer
> > > uses XS-Vcs-Svn extensively, but I would like to add XS-Vcs-Bzr. Aside
> > > from the fact that having both simultaneously would be ambiguous and
> > > confusing, there's a possibility that both Debian and Ubuntu are using a
> > > bzr branch. I'd suggest XS-Original-Vcs-* except I never did figure out
> > > why we used Original rather than Debian there, and it's even more likely
> > > that Ubuntu derivatives will want to change XS-Vcs-* than Maintainer,
> > > given our goals for bzr integration. Can I suggest that we standardise
> > > on renaming any existing XS-Vcs-* field to XS-Debian-Vcs-*?
> > 
> > We used Original rather than Debian because we import packages from sources
> > other than Debian.
> 
> I hadn't heard of any other sources objecting to us failing to change
> their Maintainer fields.

Our solution for Debian was to automatically change this field when
building.  Since the build system doesn't know where the package came from,
it uses the same field name for all packages.  We wouldn't want to say
Debian-Maintainer for packages which didn't come from Debian.

-- 
 - mdz