(+CC more debian folks)
On Fri, Mar 8, 2019 at 9:45 PM Enrico Weigelt, metux IT consult
wrote:
>
> Hi folks,
>
>
> here're some patches for polishing up the Debian packaging stuff,
> so it can be directly used w/ usual Debian machinery like
> pbuilder, git-buildpackage, dck-buildpackage, etc.
>
On 08.03.19 22:57, Theodore Ts'o wrote:
> The full debian directory lands in the O= directory. So presumably
> you could make it work for use case if there was a "make O=/build/dir
> debian-prepare" which copies the necessary debian/ files into the
> build directory and then someone could cd
On Fri, Mar 08, 2019 at 10:10:19PM +0100, Enrico Weigelt, metux IT consult
wrote:
> > So I really hope your patches don't break this.
>
> It shouldn't (at least I dont intend to). Haven't tried where exactly
> the generated debian/rules file lands in your case.
The full debian directory lands
On 08.03.19 18:57, Theodore Ts'o wrote:
> On Fri, Mar 08, 2019 at 01:44:19PM +0100, Enrico Weigelt, metux IT consult
> wrote:
>> One point still puzzling me: once the debian/rules is applied and
>> somebody calls `make deb-pkg`, he'll end up w/ unclean tree, as
>> now a git-tracked file is
On Fri, Mar 08, 2019 at 01:44:19PM +0100, Enrico Weigelt, metux IT consult
wrote:
> One point still puzzling me: once the debian/rules is applied and
> somebody calls `make deb-pkg`, he'll end up w/ unclean tree, as
> now a git-tracked file is changed.
This is not something I've noticed, but I
Hi folks,
here're some patches for polishing up the Debian packaging stuff,
so it can be directly used w/ usual Debian machinery like
pbuilder, git-buildpackage, dck-buildpackage, etc.
These expect debian/rules to exist in the unpacked/patched tree
and drive the whole build. Currently 'make
6 matches
Mail list logo
