v3 Debian source package formats
Manoj Srivastava
srivasta at acm.org
Thu Oct 2 18:33:00 UTC 2008
On Thu, Oct 02 2008, George Danchev wrote:
> Quoting Manoj Srivastava <srivasta at acm.org>:
>
> --cut--
>> Well, You look at the public branches to see the divergence. and
>> if you think my repo does not match the sources (which is a trust
>> issue, I suppose), You'll have ot do whatever you need to, since
>> obviously you do not believe my tagging.
>
> Multiply that with the number of your possible users, and you will see
> what a giant time-waste is.
I do not see a major use case for distrusting the developer as
the basis of collaboration.
>> Frankly, none of the things you are saying make a compelling
>> argument for quilt. madduck makes a better case.
>
> Nobody is comparing git with quilt, really. Obviously you are trying
> to compare different unit types as a result of muddle thinking. It is
> not git *or* quilt, but DVCS *and* some sort of patch series and I see
> LKML and git developers constantly performing that. So, forget about
> quilt and think of the least common multiple as an abstract change
> units every can inherit and extend.
Fine. Then I posit that the best way to help people is to give
them the same environment that I work with (preferred form of
modification and all). This means putting in ./debian/topic a patchset
for each pure featrue branch, that is not serialized, so people can
try out each fauture by itself, makes it easier for upstream or
downstream to get a single feature cherry picked.
The diff.gz is then the integration branch, and produces the
sources that the package was built from.
The one thing you lose is the serialization changes (the efort
that is spent in serializing the features).
Given the advantages (ability to checkout any feature
independently, exact replication of the developers working
environment), I am willing to fail on the linkage between feature
branches and the integration branch being re-done on the fly during
build.
manoj
--
After the last of 16 mounting screws has been removed from an access
cover, it will be discovered that the wrong access cover has been
removed.
Manoj Srivastava <srivasta at acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
More information about the vcs-pkg-discuss
mailing list