From: Michal Marek <mmarek@suse.cz>
To: "Marciniszyn, Mike" <mike.marciniszyn@intel.com>
Cc: Doug Ledford <dledford@redhat.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: Fri, 05 Jul 2013 22:29:50 +0200 [thread overview]
Message-ID: <51D72CBE.7070502@suse.cz> (raw)
In-Reply-To: <32E1700B9017364D9B60AED9960492BC2115D782@FMSMSX107.amr.corp.intel.com>
Dne 5.7.2013 15:04, Marciniszyn, Mike napsal(a):
>> For consistency and compatibility with older tar versions, please use
>> $RCS_TAR_EXCLUDE instead of --exclude-vcs. Also, you only need .config,
>> scripts/, include/ and the Makefiles to build external modules. But that's an
>> optimization that can be done in a later patch.
>>
>
> I can't find any reference to the above string in kernel Makefiles or tar info?
>
> Do you have more details?
It's $RCS_TAR_IGNORE, sorry.
>>> +echo "%post devel"
>>> +echo "cd /lib/modules/$KERNELRELEASE"
>>> +echo "ln -sf /usr/src/kernels/$KERNELRELEASE build"
>>> +echo "ln -sf /usr/src/kernels/$KERNELRELEASE source"
>>> +echo ""
>>> +echo "%postun devel"
>>> +echo "cd /lib/modules/$KERNELRELEASE"
>>> +echo "rm -f build source"
>>
>> These symlinks should be part of the RPM payload.
>
> I guess the %post* sections would then be not needed...
Yes.
Michal
next prev parent reply other threads:[~2013-07-05 20:29 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 [this message]
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
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=51D72CBE.7070502@suse.cz \
--to=mmarek@suse.cz \
--cc=dledford@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=mmarcini@yahoo.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