Hello, On Mon, Dec 04 2017, Ian Jackson wrote:
> OTOH, if you are not trying to build for upload, then then there is no > need for this. Then it would be better not to use dgit build at all, > but rather to invoke dpkg-buildpackage. > > Perhaps it would be useful for dgit to have a "not (yet) for upload" > build option, which generates source and binary packages, but not a > .changes file. > > What do you think ? This would just be an alias for existing commands like `debuild -uc -b` and `debuild -us -uc -S`, modulo deleting the .changes file. I don't think it would be helpful for people trying to understand dgit if there were subcommands that didn't actually have anything to do with dgit, simply being aliases for non-dgit commands. (I'd also like to request that if you do want to add such a command, you first apply at least some of the commits in #848931 which touch the code for the building commands.) > TBH I would like to know what you were trying to do when you > encountered this problem - and which docs you read that led you to > choose this approach. > > I would like to improve the docs. It might be sufficient just to add a warning "note that this accesses the network. If you want to do a purely offline build, invoke dpkg-buildpackage or debuild directly" (I wouldn't mention sbuild, because by default sbuild also accesses the network to update your schroot). -- Sean Whitton
signature.asc
Description: PGP signature
