Once upon a time, Daniel wrote :
>  > And yes, I accept patches/comments/suggestions about all those spec
>  > files!
>
> Sure thing :)
Cool :-)
> I've added to the spec some flags to remove OSS and ISA-PNP support at
> build time if one wishes to, so is's possible to do a
>
> 	rpmbuild --recompile <rpm> --without oss --without isapnp
OK, I'll add this.
> Also, having the kernel compiled by me, I have no kernel-source package
> installed.  I've added a flag "kernsrc", that also can be used
> --without, to remove the dependency for kernel-source at build time.  It
> would be nice to check the correct kernel include files actually exist
> (/lib/modules/`uname -r`/build/include/linux/*.h), though; however, I'm
> a beginner in RPM building -- is it possible to BuildRequire for a file
> not provided by a package at all?  I've googled a bit, and found no way
> to do that.
Requiring a file that isn't part of an rpm is not possible, no, except
maybe by stopping the build process if it isn't found... but that's errr...
ugly!
And I really think that for people who installed a kernel from sources, the
easiest is to install the alsa kernel drivers from source too...
> I was also considering adding some sort of flag for the --with-cards
> option in alsa's ./configure, but don't know how to do that.  Only found
> out about --without from your first alsa-driver.spec, and existing RPM
> docs don't help much.
This would be a tricky one since to use the "--with <name>" feature of
rpmbuild, I think you'd need to add individual handling of each and every
card :-/
> Oh, and one more thing :).  At first I've installed the first version of
> alsa-driver for 2.4.18-10, although I don't have that kernel, to supply
> the dependency for the rest of the alsa rpm's, and compiled the modules
> from source.  It created the /dev files and all.
That's what the "alsa-driver" is there for, create all the base files
excluding the kernel drivers. What I would suggest for dependency reasons
it to install an "alsa-kernel" for the original kernel (you've kept it,
right? ;-)) and install ALSA modules from source for custom kernels built
from source.
> Then wanted to make my own rpm for 2.4.19, so now I'm trying to rpmbuild
> the alsa-kernel package.  Removed all alsa rpms, and tried my spec:
>
> rpmbuild --ba alsa-driver.spec.mine --without oss --without isapnp
> --without kernsrc
>
> But I get this:
>
> ==[long successful compile snipped]=====================================
> RPM build errors:
>       File listed twice: /dev/adsp
>       File listed twice: /dev/amidi
>       Installed (but unpackaged) file(s) found:
>      /etc/makedev.d/00macros
>      /etc/rc.d/init.d/alsasound
> ========================================================================
>
> Oh, and I think I've forgot to mention, I'm running beta-null :).
Indeed : The rpm 4.1 snapshot in (null) has a few new features among which
having the build fail when files are present in the build root but not
listed in the %files section. I should remove them manually as part of the
build process... or maybe the new "%exclude /path/to/file" in the %files
section would do, but I don't know how older versions of rpm would handle
it. On my (null) build system, I've simply set the variable :
%_unpackaged_files_terminate_build 0
Matthias
--
Matthias Saou                                World Trade Center
-------------                                Edificio Norte 4 Planta
System and Network Engineer                  08039 Barcelona, Spain
Electronic Group Interactive                 Phone : +34 936 00 23 23
_______________________________________________
RPM-List mailing list <RPM-List@freshrpms.net>
http://lists.freshrpms.net/mailman/listinfo/rpm-list