Guillem Jover dixit:

>Well, yes and no. This was brought up on IRC by Ansgar when this new
>behavior showed up. The problem here is that you are building a source
>package by making a source-only build, disabling dependency checks and
>cleanup, which means the debian/files gets left behind.

I am disabling running 'debian/rules clean' (usually because the
packages have Build-Depends my workstation cannot fulfil), not
disabling dpkg cleaning up its own files _after_ the fact.

Well, that was my intent anyway.

>If what you want is to just create a source package then the correct
>thing to do IMO is to just run dpkg-source --build. Of course you
>might also need to run dpkg-source --before-build and --after-build.

To remember all these is kinda dpkg-buildpackage’s job…

>But not running clean and expecting things to stay clean seems a bit
>too much hopeful! :)

Well, the option is documented as “no-pre-clean”. Maybe I’m also using
the wrong option, tell me… I generally use it only if building a source
package from a clean VCS tree (to throw into cowbuilder or do a source-
only upload) when “debian/rules clean” would error out (e.g. because it
use(s|d to use) dh-systemd which I cannot install on the host system).

In general, this works except for .pc/ and now debian/files.

Might be useful to split them, maybe? -nc disables running d/r clean,
and a new option -nC also disables removing these?

>In principle for 1.19.x, I'd like to move all generated cruft to
>something like debian/.build/ or similar, which means we could add
>this to our VCS ignore rules and the above would "work". But otherwise

I really prefer a lot to still have those files removed… I’d not
ignore them but grumble and remove them after dpkg-buildpackage
anyway, so please no. (Also, for git, ignored files generally stick
around when switching branches, which may be annoying later too.)

Thanks,
//mirabilos
-- 
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend.           -- Andreas Bogk über boehm-gc in d.a.s.r

Reply via email to