I volunteer

[Jack Neely]

Folks,

So I'm still confused about this?  Am I misunderstanding something?  Do
I need to clarify?

Jack Neely

> 
> So I have a question about the package naming guidelines.
> 
> I'm using yum.
> 
> A common thing is to push out a new kernel update for security reason 42
> and in the same push push out a complete set of openafs-* packages.  The
> new openafs-kernel packages work with the new kernel and require that
> kernel version.
> 
> With the Fedora naming scheme the openafs-kernel packages turn into
> kernel-module-openafs-2.4.20-19.9 and do not require a kernel version.
> 
> So unless there's another requires somewhere to require the provided
> kernel-module-openafs = %{epoch}:%{version}-%{release} how does the new
> OpenAFS package get upgraded?
> 
> I guess in my case I can have openafs-client do the above require.
> (Right now it only requires %{version}.)
> 
> What if I was shipping something that was just a kernel module and not
> other accompanying packages?
> 
> Jack Neely
> 
> 
> -- 
> Jack Neely <slack at quackmaster.net>
> Realm Linux Administration and Development
> PAMS Computer Operations at NC State University
> GPG Fingerprint: 1917 5AC1 E828 9337 7AA4  EA6B 213B 765F 3B6A 5B89
> 
> 
> --
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> http://www.redhat.com/mailman/listinfo/fedora-devel-list
> 

-- 
Jack Neely <slack at quackmaster.net>
Realm Linux Administration and Development
PAMS Computer Operations at NC State University
GPG Fingerprint: 1917 5AC1 E828 9337 7AA4  EA6B 213B 765F 3B6A 5B89