From: Theodore Ts'o <tytso@mit.edu>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: "Enrico Weigelt, metux IT consult" <info@metux.net>,
<linux-kernel@vger.kernel.org>, <yamada.masahiro@socionext.com>,
<michal.lkml@markovi.net>, <apw@canonical.com>, <joe@perches.com>,
<linux-kbuild@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: Debian build polishing
Date: Fri, 8 Mar 2019 16:57:24 -0500 [thread overview]
Message-ID: <20190308215724.GA22319@mit.edu> (raw)
In-Reply-To: <fe53cd84-5953-786a-3a4f-6eac652a1cdd@metux.net>
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 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 into /build/dir and run
"dpkg-buildpackage"?
- Ted
next prev parent reply other threads:[~2019-03-08 21:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 12:44 Debian build polishing Enrico Weigelt, metux IT consult
2019-03-08 12:44 ` [PATCH v1 1/5] Makefile: rules for printing kernel architecture and localversion Enrico Weigelt, metux IT consult
2019-03-08 12:44 ` [PATCH v1 2/5] scripts: mkdebian: allow renaming generated debian/rules via env Enrico Weigelt, metux IT consult
2019-03-08 12:44 ` [PATCH v1 3/5] scripts: mkdebian: fix missing dependencies Enrico Weigelt, metux IT consult
2019-03-08 12:44 ` [PATCH v1 4/5] scripts: checkpatch.pl: don't complain that debian/rules is executable Enrico Weigelt, metux IT consult
2019-03-08 14:13 ` Joe Perches
2019-03-08 12:44 ` [PATCH v1 5/5] debian: add generic rule file Enrico Weigelt, metux IT consult
2019-03-08 17:57 ` Debian build polishing Theodore Ts'o
2019-03-08 21:10 ` Enrico Weigelt, metux IT consult
2019-03-08 21:57 ` Theodore Ts'o [this message]
2019-03-10 18:50 ` Enrico Weigelt, metux IT consult
2019-03-11 16:19 ` Masahiro Yamada
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190308215724.GA22319@mit.edu \
--to=tytso@mit.edu \
--cc=apw@canonical.com \
--cc=info@metux.net \
--cc=joe@perches.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkml@metux.net \
--cc=michal.lkml@markovi.net \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).