From: pwd@mdtsoft.com
To: kaos@ocs.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Update to the make rpm system kernel 2.4.17 and 2.5.1
Date: Mon, 7 Jan 2002 13:07:10 -0500 (EST) [thread overview]
Message-ID: <200201071807.g07I7AL08968@mdtsoft.com> (raw)
In-Reply-To: <7074.1010210531@ocs3.intra.ocs.com.au>
On 5 Jan, Keith Owens wrote:
> On Fri, 4 Jan 2002 15:05:37 -0500 (EST),
> pwd@mdtsoft.com wrote:
>>I needed to be able to build a bit more complex set of rpm files than
>>the make rpm function allowed. Attached is a patch that will replace
>
> In kernel build 2.5 the make rpm target does not exist. kbuild 2.5
> builds the kernel and modules, installs the kernel, modules, System.map
> and .config, that is _all_ it does. Extra tasks like updating
> bootloader files or building a package using the packaging method of
> the month are _not_ part of kbuild 2.5. Every user wants to do
> something different with bootloaders and packaging, there is no "one
> size fits all" script.
>
>
The reason for the improved rpm build process is not per say for distrubutation
builders; it is for users who have a number of systems to manage and don't want
to have non package things floating around.
That said it looks like the best thing for me to do might be to move the "make rpm"
function out of the Makefile and into a seperate script when kbuild 2.5 is
made live in the main line. The rpm build does not use the make system to
build first phase and after that is under the control of RPM itself.
I assume that the xconfig, oldconfig, config and mconfig are present in
kbuild 2.5?
What is the correct method to tell if 2.5 is live?
--
It is MDT, Inc's policy to delete mail containing unsolicited file attachments.
Please be sure to contact the MDT staff member BEFORE sending an e-mail with
any file attachments; they will be able to arrange for the files to be received.
This email, and any files transmitted with it, is confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please advise postmaster@mdtsoft.com
<mailto:postmaster@mdtsoft.com>.
Philip W. Dalrymple III <pwd@mdtsoft.com>
MDT Software - The Change Management Company
+1 678 297 1001
Fax +1 678 297 1003
next prev parent reply other threads:[~2002-01-07 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 20:05 [PATCH] Update to the make rpm system kernel 2.4.17 and 2.5.1 pwd
2002-01-05 6:02 ` Keith Owens
2002-01-07 18:07 ` pwd [this message]
2002-01-07 20:22 ` Keith Owens
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=200201071807.g07I7AL08968@mdtsoft.com \
--to=pwd@mdtsoft.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.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