From: Frans Pop <elendil@planet.nl>
To: maximilian attems <max@stro.at>
Cc: linux-kbuild@vger.kernel.org, sam@ravnborg.org
Subject: Re: [PATCH] deb-pkg: Make deb-pkg generate a seperate linux-libc-dev deb
Date: Thu, 5 Nov 2009 01:31:01 +0100 [thread overview]
Message-ID: <200911050131.02305.elendil@planet.nl> (raw)
In-Reply-To: <20091104234023.GJ29378@baikonur.stro.at>
On Thursday 05 November 2009, maximilian attems wrote:
> On Thu, Nov 05, 2009 at 12:19:59AM +0100, Frans Pop wrote:
> > maximilian attems wrote:
> > > userland dev likes latest incarnation of that userland API.
> > > make it easy to also build it on make deb-pkg invocation:
> >
> > I would very much prefer it if this was either optional or a separate
> > target. I have personally never had any need for such a package and
> > would like to be able to not build it.
> >
> > I agree it should be possible, just not forced.
>
> so what you propose a bindeb-pkg target for the linux-image only?
Yep, that would be fine as a solution and consistent with the targets for
rpm. Probably bindeb-pkg should do image + firmware though?
> there is clearly demand for linux-source and linux-headers packages
> build out of deb-pkg.
No disagreement with that.
Cheers,
FJP
next prev parent reply other threads:[~2009-11-05 0:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 22:30 [PATCH] deb-pkg: Make deb-pkg generate a seperate linux-libc-dev deb maximilian attems
2009-11-04 22:39 ` maximilian attems
2009-11-04 23:19 ` Frans Pop
2009-11-04 23:40 ` maximilian attems
2009-11-05 0:31 ` Frans Pop [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-01 15:44 maximilian attems
2011-01-07 14:02 ` Michal Marek
2011-01-07 15:15 ` maximilian attems
2011-01-07 15:27 ` Michal Marek
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=200911050131.02305.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kbuild@vger.kernel.org \
--cc=max@stro.at \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox