Rene Engelhard ha scritto:
Hi,
On Fri, Nov 20, 2009 at 11:28:56AM +0100, Marco Nenciarini wrote:
3) When a new version of a component is released, how to handle it in
the new source format? I can't find any standard place where to put meta
informations regarding extra origin tarball.
Marco Nenciarini mnen...@debian.org writes:
Rene Engelhard ha scritto:
Hi,
On Fri, Nov 20, 2009 at 11:28:56AM +0100, Marco Nenciarini wrote:
3) When a new version of a component is released, how to handle it in
the new source format? I can't find any standard place where to put meta
Goswin von Brederlow ha scritto:
Marco Nenciarini mnen...@debian.org writes:
I think the right way to include a new component or to update one is to
bump the package source version. Something like:
dovecot_1.2.7+plugin1.orig-libsieve.tar.gz
This avoids to let dpkg-source (and the
Hi,
On Fri, Nov 20, 2009 at 11:28:56AM +0100, Marco Nenciarini wrote:
3) When a new version of a component is released, how to handle it in
the new source format? I can't find any standard place where to put meta
informations regarding extra origin tarball.
I don't think there exist one.
On Fri, Nov 20, 2009 at 11:28:56AM +0100, Marco Nenciarini wrote:
2) Talking of an hypothetic VCS-buildpackage using pristine-tar or
similar tools, how it can known which component tarball need it to
extract to create the right build environment? May be we should
define a standard place under
On Fri, Nov 20, 2009 at 11:28:56AM +0100, Marco Nenciarini wrote:
Hi,
I'm working on switching dovecot package to format 3.0 (quilt) and I
wish to use the multi-origin option, because it comes as three source
tar.gz [1][2][3] plus a patch [4].
I've done the initial switch [5] and it
6 matches
Mail list logo
