All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: riku.voipio@linaro.org, linux-kbuild@vger.kernel.org,
	debian-kernel@lists.debian.org,
	Chris J Arges <chris.j.arges@canonical.com>,
	maximilian attems <maks@stro.at>
Subject: Re: [PATCH v3] deb-pkg: add source package
Date: Wed, 19 Aug 2015 15:36:59 +0200	[thread overview]
Message-ID: <55D4867B.40802@suse.cz> (raw)
In-Reply-To: <1434010298-21445-1-git-send-email-riku.voipio@linaro.org>

On 2015-06-11 10:11, riku.voipio@linaro.org wrote:
> From: Riku Voipio <riku.voipio@linaro.org>
> 
> Make deb-pkg build both source and binary package like make rpm-pkg does.
> For people who only need binary kernel package, there is now bindeb-pkg
> target, same target also used to build the .deb files if built from the
> source package using dpkg-buildpackage.
> 
> Generated source package will build the same kernel .config than what
> was available for make deb-pkg. The name of the source package can
> be set with KDEB_SOURCENAME enviroment variable.
> 
> The source package is useful for gpl compliance, or for feeding to a
> automated debian package builder.
> 
> Cc: Chris J Arges <chris.j.arges@canonical.com>
> Cc: maximilian attems <maks@stro.at>
> Cc: Ben Hutchings <ben@decadent.org.uk>
> Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
> ---
> v3,
>  * Allow setting source package name with KDEB_SOURCENAME
>  * Fix issues noted by Ben: drop python and fix target in debian/rules
>  * Merge "ensure $MAKE can use jobserver" oneliner from Chris J Arges

Ben,

are you OK with the v3 of this patch?

Thanks,
Michal

  reply	other threads:[~2015-08-19 13:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  8:11 [PATCH v3] deb-pkg: add source package riku.voipio
2015-08-19 13:36 ` Michal Marek [this message]
2015-08-21  9:08   ` Ben Hutchings
2015-08-21 12:38     ` Michal Marek
2015-08-21 14:40       ` Riku Voipio

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=55D4867B.40802@suse.cz \
    --to=mmarek@suse.cz \
    --cc=ben@decadent.org.uk \
    --cc=chris.j.arges@canonical.com \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=maks@stro.at \
    --cc=riku.voipio@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.