From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: [RFC PATCH 0/1] kernel.bbclass: add non-santized kernel provides
Date: Fri, 6 Jul 2012 11:52:40 -0400 [thread overview]
Message-ID: <1341589961-14331-1-git-send-email-bruce.ashfield@windriver.com> (raw)
Richard/Saul,
I'm sending this out as a RFC, since I'm far from a packaging
expert. I've got all the details in the patch, but I ran into
a situation where the version string in utsrelease.h was being
santized for the kernel provides, and not in the kernel module
requires.
I tried several solutions:
- Changing the kernel module requires (more complex, more
code involved)
- Adding an extra provides in the kernel recipe with the
version string (only fixes my problem and doens't help
others)
- Changing the string to something that doesn't change
(aka run and hide)
- Adding a secondary provides in the kernel RPM so both
the sanitized and raw package name are present. This
was a small fix, works for my nasty version string, and
for the normal strings that I have elsewhere. It also
keeps existing provides intact in case something else I
can't see depends on the behaviour.
If the change seems reasonable, I can send a pull request
(or merge it directly if you want :) .. but I'm definitely open
to hearing about better solutions as well.
Cheers,
Bruce
next reply other threads:[~2012-07-06 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 15:52 Bruce Ashfield [this message]
2012-07-06 15:52 ` [PATCH] kernel.bbclass: add non-santized kernel provides Bruce Ashfield
2012-07-09 16:54 ` Saul Wold
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=1341589961-14331-1-git-send-email-bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.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