From: "Bjørn Mork" <bjorn@mork.no>
To: maximilian attems <max@stro.at>
Cc: "Martin-Éric Racine" <martin-eric.racine@iki.fi>,
"Jonathan Nieder" <jrnieder@gmail.com>,
linux-kbuild@vger.kernel.org, debian-kernel@lists.debian.org
Subject: Re: [PATCH] scripts/package/builddeb: upgrade to current practices
Date: Wed, 18 Jul 2012 09:47:37 +0200 [thread overview]
Message-ID: <87629lbjdy.fsf@nemi.mork.no> (raw)
In-Reply-To: <20120718065615.GW28778@vostochny.stro.at> (maximilian attems's message of "Wed, 18 Jul 2012 06:56:15 +0000")
maximilian attems <max@stro.at> writes:
> Jonathan already answered it, saying that firmwares are put
> in versioned dir.
>
> Just use git to look it up, easy:
> ~/src/linux-next (master %=)$ git log scripts/package/builddeb
>
> 6607ddadf93d19c7f64139f1475c342152f39fe5
But..but.. won't that prevent installing firmware for more than one
builddeb kernel? I.e., shouldn't the fw package name also be versioned
if you are going to do this (which it seems you are)?
But then again, I thought versioned firmware was dropped from the
official packages for good reasons. Any reason why you couldn't add
/lib/firmware/something (where "something" is fixed and independent of
version) to the firmware.agent search path, and use that for unofficial
linux-firmware packages?
That would allow unofficial firmware packages from different kernel
versions to continue sharing their package name without conflicting with
the official packages in any way.
Bjørn
next prev parent reply other threads:[~2012-07-18 7:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 17:57 [PATCH] scripts/package/builddeb: upgrade to current practices Martin-Éric Racine
2012-07-17 19:39 ` Jonathan Nieder
2012-07-17 19:46 ` Martin-Éric Racine
2012-07-17 21:23 ` maximilian attems
2012-07-17 23:19 ` Martin-Éric Racine
2012-07-17 23:27 ` Jonathan Nieder
2012-07-18 6:56 ` maximilian attems
2012-07-18 7:21 ` Martin-Éric Racine
2012-07-18 8:05 ` Bjørn Mork
2012-07-18 7:47 ` Bjørn Mork [this message]
2012-08-14 15:46 ` Jan Engelhardt
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=87629lbjdy.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=debian-kernel@lists.debian.org \
--cc=jrnieder@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=martin-eric.racine@iki.fi \
--cc=max@stro.at \
/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.