No, hits=0.2 required=5.0
	tests=KNOWN_MAILING_LIST,RCVD_IN_MULTIHOP_DSBL,
	      RCVD_IN_UNCONFIRMED_DSBL,USER_AGENT,USER_AGENT_MOZILLA_UA,
	      X_ACCEPT_LANG
	version=2.50-cvs

I use a mostly Red Hat 8.0 system, but prefer to configure and build my
kernel by hand.  I'd like to humbly offer a tweak to alsa-driver.spec
that helps it build cleanly under such circumstances.  I recognize that
freshrpms.net packages are designed with standard Red Hat in mind,
including a standard kernel RPM.  However, I hope that Matthias will
consider the tweak small enough to justify its incorporation.
The diff is attached below.  The first part of the diff contains a
conditional that checks to see if the expected RPM is installed.  If it
is, %{karch} is set as before and a new %{krpm} flag is set to 1.  If
the expected RPM is not installed, then %{karch} is instead set using
"uname -p", while %{krpm} is left undefined.
The second part of the diff is simpler.  We only require that
kernel-source be installed if the kernel itself came from an RPM.  (If
the kernel was hand-built, the presumably the user knows enough to have
retained the sources in the expected place.)
Again, I realize that I'm operating "off warrantee" by not using a Red
Hat kernel RPM.  Matthias, if you think this tweak is reasonable and not
too ugly, I'd love to see you pick it up.  If not, well at least this
message will sit in the archives and may help other folks in the future.

No, hits=-2.4 required=5.0
	tests=AWL,IN_REP_TO,KNOWN_MAILING_LIST,NOSPAM_INC,
	      QUOTED_EMAIL_TEXT,RCVD_IN_RFCI,REFERENCES,
	      REPLY_WITH_QUOTES,SIGNATURE_SHORT_SPARSE
	version=2.50-cvs

Once upon a time, Ben wrote :
> I use a mostly Red Hat 8.0 system, but prefer to configure and build my
> kernel by hand.  I'd like to humbly offer a tweak to alsa-driver.spec
> that helps it build cleanly under such circumstances.  I recognize that
> freshrpms.net packages are designed with standard Red Hat in mind,
> including a standard kernel RPM.  However, I hope that Matthias will
> consider the tweak small enough to justify its incorporation.
Well, I don't really find it consistent at all to use an rpm package built
against something that wasn't installed through rpm :-/
What I'd recommend in your case : You should keep at least one original Red
Hat Linux kernel (you do just in case, right? ;-)) and install the matching
alsa-kernel package as you'll need at least one because of the
dependencies. Then for your custom built kernel, simply "./configure
--with-cards=all && make && make install DESTDIR=/tmp/alsa-driver" from the
alsa-driver sources then as root copy all the modules under
/tmp/alsa-driver/lib/modules/ to your modules dir and run "depmod -a".
Of course you can even make it much faster by not compiling all un-needed
drivers, as I guess that's one of the reasons one would rebuild his own
kernel.
I find this the easiest and cleanest way to get around the problem. It's
what I've done and what I'll keep doing on my laptop where I'm running a
kernel recompiled with ACPI.
Matthias
--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Red Hat Linux release 7.3 (Valhalla) running Linux kernel 2.4.18-10acpi
Load : 0.00 0.02 0.00
_______________________________________________
RPM-List mailing list <RPM-List@freshrpms.net>
http://lists.freshrpms.net/mailman/listinfo/rpm-list