As per subject: do we already have a best practice for that?
The problem I'm trying to solve is how to know "where" to work on a
package maintained using a $DVCS. debcheckout is not enough, as it
usually checks out just one branch, which has different logics in
different packages. For example, it can be the integration branch with
changes already applied to upstream sources. Or it can be a debianized
source tree with patches under debian/patches/ which have been
_generated_ using git-format-patch (real life example: dash). Working on
these two scenarios is quite different ...
Now, we have debian/README.source, but according to my reading of policy
4.14 it is not evident that it is the right place where to document
branch layout. The only part of that which *might* be related is where
it is mentioned how to package a new upstream version.
I do not think we should try to standardize machine parseable formats
for this kind of information, a human readable file would do. And I do
think that debian/README.source is the right place, but we should
mention it explicitly in policy then.
Thoughts?
Comments?
--
Stefano Zacchiroli -*- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
I'm still an SGML person,this newfangled /\ All one has to do is hit the
XML stuff is so ... simplistic -- Manoj \/ right keys at the right time
Attachment:
signature.asc
Description: Digital signature