[OpenAFS-devel] [PATCH] change OpenAFS-1.2.10 SRPM to work better with RedHat

[Derek Atkins]

David Howells <dhowells@redhat.com> writes:

> > I agree that making it controllable from outside the spec file is a
> > good idea.  HOWEVER, for my personal sanity I'd like to be able to
> > just say "rpmbuild -ba openafs.spec" and have it build _EVERYTHING_
> > for me.
> 
> -ba does -bb + -bs.

That's not what I mean.  What I'd like is to run "rpmbuild -ba openafs.spec"
and have it generate:
        the userspace RPMS
        the SRC RPM
        and ALL the kernel RPMs for ALL installed kernels.

> There are tools for automatic package download, installation and upgrading
> (such as up2date and apt-get). Dependencies must be correctly resolvable for
> these to work.

So you're just talking about the binary module....  I have a feeling we're
talking past each other...

> So, to take a hypothetical case, if a particular RPM contains all the modules
> matching 50 different kernels, then if the dependencies are all there, then
> the automated upgrade tool will either fail or will download and install the
> 49 kernels you didn't want (if they're available). Alternatively, if the
> dependencies are missing, then the RPM will not be automatically upgraded with
> the kernel.

... and I STILL think we're talking past each other here...

> > > Although it might be nice to have the spec file generate an arbitrary list
> > > of RPMs for the various kernels that it can only find out about by listing
> > > /lib/modules, I don't think it's possible from within the spec file.
> > 
> > Why not?  I did it before...  ;)
> 
> How? It's not in 1.2.9 or .10. That produces a fixed set of RPMs, including a
> single RPM with all the OpenAFS kernel modules contained within.

... and now I'm convinced we're talking past each other.

Let me re-explain what I'm asking about.  What I want is a
consolidated "openafs.spec" which performs the actions that I stated
above.  I'm perfectly happy having multiple kernel-module RPMS, one
for each kernel.  That's fine with me (and something I wanted to do
anyways).  However, I also want a single openafs.spec which will
recursively build all the kernel modules for all installed kernels.

I do NOT want to have to write a script that builds everything -- I
want the specfile to have that logic internally (even if it means
calling itself recursively).

> David

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available