From: "L. Alberto Giménez" <agimenez@sysvalve.es>
To: Riku Voipio <riku.voipio@linaro.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] build: Exclude cscope and tags files from packaging
Date: Thu, 24 May 2018 10:47:55 +0200 [thread overview]
Message-ID: <20180524084754.GA10037@bart.evergreen.loc> (raw)
In-Reply-To: <CAAqcGH=PuRgsDU81R5P=_JSvV+vVqntBO6ivEpY2v8AqKAuGsQ@mail.gmail.com>
On Mon, May 21, 2018 at 04:06:15PM +0300, Riku Voipio wrote:
> On 17 May 2018 at 16:48, L. Alberto Giménez <agimenez@sysvalve.es> wrote:
> > When building a Debian package, cscope and tags generated files are
> > accounted in the Debian packaging process, even causing some errors
> > under some circumstances (generating diff between "pristine" tar and
> > "patched sources").
>
> Honestly you should use make mrproper, if you want to spin out source
> packages. If otoh you don't have a use for the source package, use
> bindeb-pkg.
Well, to be honest I just wanted a .deb file to distribute to my VM in order to test
and squash some bugs quickly, and in my machine, it was causing a recompilation every
time I tried to build a new package, (26 minutes withh allyes).
I just wanted to speed up things and avoid the full compilation that deb-pkg was
doing (and mrproper would cause anyway) if I already had everything done.
But I realized that bindeb-pkg does just what I want, so you can ignore this patch,
sorry for the inconvenience.
Regards,
--
L. Alberto Giménez
GnuPG key ID 0xDD4E27AB
prev parent reply other threads:[~2018-05-24 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 13:48 [PATCH] build: Exclude cscope and tags files from packaging L. Alberto Giménez
2018-05-21 13:06 ` Riku Voipio
2018-05-24 8:47 ` L. Alberto Giménez [this message]
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=20180524084754.GA10037@bart.evergreen.loc \
--to=agimenez@sysvalve.es \
--cc=linux-kbuild@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=riku.voipio@linaro.org \
--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