Re: debuild/dpkg-buildpackage behaves not as expected
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 17/05/12 11:39, James McCoy a écrit :
> On Thu, May 17, 2012 at 08:21:23AM +0200, Thibaut Paumard wrote:
>> Le 17/05/12 00:25, James McCoy a écrit :
>>> On Wed, May 16, 2012 at 04:23:05PM +0200, Olе Streicher wrote:
>>>> Unpatching the sources *before* the build process was cleaned
>>>> up makes no sense to me at all. Could you provide a use case
>>>> for that?
>>>
>>> As was described in #649531:
>>>
>>> vcs clone <repository with unpatched source> cd repo ... tweak
>>> a little ... dpkg-buildpackage; # applies patches, builds, and
>>> unapplies patches
>>
>> Precisely, the point is that should be: applies patches, builds,
>> *cleans* and unapplies patches
>
> So, you would want dpkg-buildpackage to be an expensive no-op?
> Running the clean target means that you no longer have the
> artifacts produced by the build.
>
Except the built packages in the parent directory, of course.
I see two reasonable choices:
1- don't clean, don't unpatch
2- clean, unpatch (like with -tc)
The current default (don't clean, unpatch) doesn't sound as a very
good choice to me, but again I may fail to see a use case that is
obvious to someone else.
Regards, Thibaut.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+00NQACgkQ+37NkUuUiPF1uACfTk/GvlAIJ7qLNmFzh2Xml/KP
0swAniYd9cOJJmbDkAa1gvqfS+CSRRdM
=sokZ
-----END PGP SIGNATURE-----
Reply to: