From: Doug Ledford <dledford@redhat.com>
To: Michal Marek <mmarek@suse.cz>
Cc: "Marciniszyn, Mike" <mike.marciniszyn@intel.com>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"mmarcini@yahoo.com" <mmarcini@yahoo.com>
Subject: Re: [PATCH 3/3] kbuild: add generation of kernel-devel
Date: Mon, 08 Jul 2013 12:20:28 -0400 [thread overview]
Message-ID: <51DAE6CC.2030507@redhat.com> (raw)
In-Reply-To: <51DAD082.7080700@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
On 7/8/2013 10:45 AM, Michal Marek wrote:
> On 8.7.2013 15:39, Marciniszyn, Mike wrote:
>>>
>>> rpm 4.0.3 is *ancient*. An %exclude is perfectly acceptable and definitely
>>> preferable to a broken payload.
>>>
>>
>> The top of the mkspec shell script has this comment:
>> # Output a simple RPM spec file that uses no fancy features requiring
>> # RPM v4. This is intended to work with any RPM distro.
>>
>> Are there old distros that still care about this?
>
> If it's that old, I don't think we need to care. At least not for
> building the RPM, because the compiler on such old systems is probably
> not going to be able to compile the kernel. I wasn't sure if %exclude
> wasn't added in the last five years or so.
Quick google search confirms that rpm 4.0.3 was released in December of
2001. I think it's safe to say we can use %exclude and not worry about
anything so ancient it can't support it.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2013-07-08 16:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 14:38 [PATCH 0/3] RPM enhancements for kbuild Mike Marciniszyn
2013-06-24 14:38 ` [PATCH 1/3] kbuild: add %post section to create initramfs and grub hooks Mike Marciniszyn
2013-07-23 13:19 ` Michal Marek
2013-06-24 14:38 ` [PATCH 2/3] kbuilld: install firmware files in kernel relative directory Mike Marciniszyn
2013-07-23 13:19 ` Michal Marek
2013-06-24 14:38 ` [PATCH 3/3] kbuild: add generation of kernel-devel Mike Marciniszyn
2013-07-04 15:15 ` Michal Marek
2013-07-05 13:04 ` Marciniszyn, Mike
2013-07-05 20:29 ` Michal Marek
2013-07-05 13:12 ` Marciniszyn, Mike
2013-07-05 13:17 ` Marciniszyn, Mike
2013-07-05 20:30 ` Michal Marek
2013-07-08 11:55 ` Marciniszyn, Mike
2013-07-08 12:12 ` Michal Marek
2013-07-08 13:15 ` Marciniszyn, Mike
2013-07-08 13:32 ` Doug Ledford
2013-07-08 13:39 ` Marciniszyn, Mike
2013-07-08 14:45 ` Michal Marek
2013-07-08 15:52 ` Marciniszyn, Mike
2013-07-08 16:20 ` Doug Ledford [this message]
2013-07-08 17:17 ` Marciniszyn, Mike
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=51DAE6CC.2030507@redhat.com \
--to=dledford@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=mmarcini@yahoo.com \
--cc=mmarek@suse.cz \
/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