Hi Guillem, sorry for not replying earlier & I think your wontfix is right.
On Fri, Nov 25, 2016 at 06:25:10PM +0100, Guillem Jover wrote:
> > the subject basically says it all, dpkg should not generate .buildinfo
> > files for source only uploads, as they are totally pointless for those.
> Why? I think this has come multiple times now, and I guess this needs to
> be documented in dpkg itself or a new FAQ entry be added for this. :)
yeah, probably :)
> The rationale is that, this is still a build, and Build-Depends need
> to be present, clean gets invoked which might peform non-trivial
> amounts of work, update stuff, etc before the source package gets
> built.
(btw, I see how this makes sense, though personally I'm mostly just annoyed
that I need build-depends to be installed for a source build, as I'd
like to do source builds on my normal system, where I often dont have
the right build depends available…)
> These might indeed be pointless for the reproducible project,
> but remember that this request was way older than the reproducible
> project and dpkg usually serves more general needs. ;)
right
> If people just want to build a source package, because they are
> building with say -nc -S (which implies -d too), then I think in
> general they might be better served with «dpkg-source -b» instead.
hm, I use debuild instead of dpkg-source and dpkg-buildpackage and
"debuild -b" does a binary-only build, while the "-S" does the source
only build for me… any idea how to achieve that nicely with debuild?
OTOH, I'll probably just igore .buildinfo files in these cases…
Thanks!
--
cheers,
Holger
signature.asc
Description: Digital signature
