Keith Owens <[EMAIL PROTECTED]> wrote:
> On Wed, 27 Sep 2000 10:43:38 +0200,
> "Butter, Frank" <[EMAIL PROTECTED]> wrote:
>>> How about putting these files in the modules directory? That
>>> way, we have a nice consistent location for them.
>>
>>Your assumption is that you have only one config per machine with a certain
>>kernel-release
> current method of handling multiple configs or machines leaves a bit to
> be desired. The ability to cleanly handle multiple configs, multiple
> target systems and do it all from a single source tree is on our
> wishlist for the 2.5 Makefile rewrite.
The best idea is to autmatically add some kind of release number to the
EXTRAVERSION field.
E.g. with this patch, EXTRAVERAVERSION is the rpm release number:
------ snip ------
--- linux/Makefile~ Thu Aug 10 10:28:46 2000
+++ linux/Makefile Thu Aug 10 10:32:26 2000
@@ -238,11 +238,7 @@
$(TOPDIR)/include/linux/compile.h: include/linux/compile.h
newversion:
- @if [ ! -f .version ]; then \
- echo 1 > .version; \
- else \
- expr 0`cat .version` + 1 > .version; \
- fi
+ echo RPMRELEASE > .version
include/linux/compile.h: $(CONFIGURATION) include/linux/version.h newversion
@echo -n \#define UTS_VERSION \"\#`cat .version` > .ver
------ snip ------
and this specfile snipplet
------ snip ------
# set build number to rpm release
perl -pi -e 's/RPMRELEASE/"%{Release}"/;' Makefile
------ snip ------
You rpm package release number is your EXTRAVERSION.
(and no, simply echoing it to .version will _not_ work ;))
Christoph
--
Always remember that you are unique. Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
