On Friday 06 June 2008 12:06:55 am Miriam Ruiz wrote: > Hi all, > > It seems that the majority of people in the Team feel that option 2 > (Store the whole source there, using pristine-tar, and use git at its > full power) is the most convenient one, even though it might have some > disadvantages too. I'll give it a couple of days more just to make > sure that everyone can speak, but I think there's quite a consensus in > this. Thanks for all the input received on this matter :) > > As we will have different policies for SVN and git, it might make > sense to make a wiki document defining what is expected from a package > in each of them, and how that can be handled. In SVN whe had a policy > of debhelper+quilt+debian directory only. BTW, this allows the > possibility of adding copyright and license texts to patches (I don't > know how that would be handled in git, probably in the git log). > > It is quite logical that we keep using debhelper only (no cdbs in git > either). Also the packages in git need not use any patch system > (quilt, dpatch) as git already takes care of that. I guess > pristine-tar should also be used. Could someone with some experience > in managing packages with git step forward and try to set the basic > guidelines about how we should better handle it to get the best > results, please? Maybe Andres or Cyril? How do we plan to upload debian revisions without a patching system? Do we just reupload the tarball each time? -- Regards, Andres
Attachment:
signature.asc
Description: This is a digitally signed message part.