Requirements of a VCS packaging tool

[Jesse Keating]

On Wed, 2008-03-26 at 08:54 +0100, Stefano Zacchiroli wrote:
> 
> Ack on the basic principle. However in general it is not possible to
> require that all patches apply properly to pristine source. In some
> (rare fortunately) cases two patches will conflict with each other on
> the pristine source and you need to make one depend on the other or the
> other way round.
> 
> So I will relax your requirement stating that a patch in general should
> not depend on anything else than the pristine source, but can depend on
> some other patch which (following its dependency chain) reaches the
> pristine source.

Sure, I didn't mean to state that it's an entirely black/white thing.  I
do think though that it should be possible to mark one patch as
dependent upon another patch and so on, to leave breadcrumbs for a
developer to extract a particular changeset.

-- 
Jesse Keating
Fedora -- All my bits are free, are yours?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/attachments/20080326/2f15c184/attachment.pgp