[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Behaviour of dpkg-source with "3.0 (quilt)" and VCS and automatic patches


On Sun, 29 May 2011, Bernhard R. Link wrote:
> That sounds a bit better, but it adds even more magic to dpkg-source.
> I really miss some way to express: "In this account, do not use magic.
> If things are not correct and need fixing, tell me what is wrong and
> abort so I'll never miss it." (Actually I'd prefer it as default and
> only have it enabled by some options, but a way to globally disable
> and turn them into hard errors would would be good enough[tm].)

I don't consider "applying/unapplying patches" as magic. :-)

> > But it still happens that those patches are generated[1] when the maintainer
> > did not expect any change at all. That's why we added the option
> > --abort-on-upstream-changes for maintainers who never wants dpkg-source
> > to auto-create a patch.
> There is still no way to get this behaviour account-wide, is there?

No. Except dpkg-buildflags none of the dpkg-dev scripts support
configuration files IIRC.

Raphaël Hertzog ◈ Debian Developer

Follow my Debian News ▶ http://RaphaelHertzog.com (English)
                      ▶ http://RaphaelHertzog.fr (Français)

Reply to: