On May 17, 2013, at 01:55 PM, Scott Kitterman wrote: >So I'm all for improvement, but it should be an improvement. I'd love it if >we we using a DVCS, but I don't think full source branches are a good idea. I wonder if there is a way to have our cake and eat it too. Meaning: is there a way to stack branches such that people who only want the debian/ directory can work in one branch, and people who want the full sources can work in a different branch? I honestly have no idea whether this can be done with git or any other dvcs. Scott knows that I like full source repositories, because I use Ubuntu's UDD process and am pretty happy with it. But I also acknowledge that others don't like to work with full source, and that's fine, or at least would be if we could guarantee that both styles could be used *and* that all the relevant branches would remain absolutely in sync. Full source repositories definitely do have issues, at least as manifest in UDD and in the presence of quilt patches and such. Bandwidth can also be an issue. I've mostly learned how to deal with all of these and I do think they'd be solvable if enough (or any) resources were applied to the problems, but that isn't likely going to happen. I'd swallow my dislike of git if the promise of dvcs-based package development could be realized. I also think that any sufficiently motivated developer doesn't need official blessing (whatever that even means) of the Debian Python teams to prove that it can work. Please do read the previous threads where a lot of the technical details and requirements were hashed out. This isn't something that will succeed with a weekend's worth of work. -Barry
Attachment:
signature.asc
Description: PGP signature