On 12-Mar-2009, Russ Allbery wrote: > Manoj Srivastava <srivasta@debian.org> writes: > > > b) If there is a new upstream version, cd checked out dir > > 1. No munging required: use uscan --rename --verbose to get the > > latest source. > > 2. Munging needed. Run get-orig-source to get the latest upstream > > source via uscan; and munge it as needed to create the > > orig.tar.gz file > > Oh, okay, so your get-orig-source target would internally use uscan. > How do you tell from that what tarball it downloaded for an > automated target? Would you parse the output of uscan somehow? Also, what do you do for the cases where upstream doesn't have a tarbal (either none at all, or the code you want isn't yet available as a tarball)? Or do you (Manoj) not have any upstream packages making original source available as anything but tarball releases? > I never use uscan --download; I always download the new upstream > source myself using wget or a web browser or FTP client. Why is that? Is there some downside to using ‘uscan --download’? I would have thought it best to use the automated tool where possible, if for no other reason than to make sure the automated process will get the same source you're working with. -- \ “I was born by Caesarian section. But not so you'd notice. It's | `\ just that when I leave a house, I go out through the window.” | _o__) —Steven Wright | Ben Finney <ben@benfinney.id.au>
Attachment:
signature.asc
Description: Digital signature