Hello, On Sun, Aug 13 2017, Ian Jackson wrote:
> Parsing the arguments to other programs is quite a lot of work and > makes for a fragile program. Normally, where I can, I have taken a > different approach: provide a specific option to dgit that 1. causes > the corresponding argument to be passed to a subprogram and 2. makes > whatever other changes are ncecessary. Right, but on Sam's suggestion all you'd be matching is --git-builder -- no parsing of the builder command. > I think the right direction might be for there to be a way to tell > dgit that you are wanting to use this workflow, but perhaps indeed > running origtargz and the dgit sbuild will DTRT. So: dgit doesn't download the orig iff both (a) a config value is set; and (b) a pristine-tar branch (local or remote) exists. >> Though I guess you have to rm the orig that dgit downloads. > > I don't see why that would be needed. If dgit clone or dgit fetch > gets an orig, then surely it will be the same as the pristine-tar one. If there is already an orig.tar present than origtargz(1) won't overwrite it. -- Sean Whitton
