also sprach Raphael Hertzog [2010.05.28.1119 +0200]:
> No, local-options can be in the VCS, it will just not be in the
> resulting source package.
Doh! But then I suggest a different name than local-*, since that is
kinda reserved for "changes made locally that are independent of
Debian".
Why no
On Fri, 28 May 2010, martin f krafft wrote:
> also sprach Raphael Hertzog [2010.04.25.2202 +0200]:
> > It's still the right behaviour for any source package that we distribute
> > IMO. It should always be possible to modify any file and be able to
> > rebuild the source package without having an e
Before Raphaël showed me this report, I had written my own.
I include it here simply because it goes a step further than the
quilt format and advocates aborting in the presence of any changes
outside debian/*:
An option like --refuse-debian-patch (v3 mainly) or
--refuse-non-debian-changes (mor
also sprach Raphael Hertzog [2010.04.25.2202 +0200]:
> It's still the right behaviour for any source package that we distribute
> IMO. It should always be possible to modify any file and be able to
> rebuild the source package without having an error.
>
> Thus if I add such an option it would onl
Hi,
On Sat, 24 Apr 2010, Kurt Roeckx wrote:
> It's currently auto creating patches for things that changed
> compared to the upstream version. I find it rather annoying,
> because most of the time it's something left behind that just
> needed to be cleaned up, like a .orig or .rej file or somethi
Package: dpkg-dev
Version: 1.15.7.1
Severity: wishlist
Hi,
It's currently auto creating patches for things that changed
compared to the upstream version. I find it rather annoying,
because most of the time it's something left behind that just
needed to be cleaned up, like a .orig or .rej file or
6 matches
Mail list logo
