[OpenAFS-devel] Fully Functional Client on Linux 2.6

[Jack Neely]

On Fri, Jul 02, 2004 at 07:11:29PM -0400, Matthew Miller wrote:
> On Fri, Jul 02, 2004 at 06:36:02PM -0400, Derek Atkins wrote:
> > Sure they will!  Indeed this is what I'd like to (eventually)
> > implement, ala the patches sent here months ago to build just a kernel
> > package.  This way when a new kernel is released you can just build a
> > new kernel package for that new kernel version without having to
> > rebuild the whole source tree.
> 
> So the kernel packages will have a different spec file and everything?
>

Nope.  Subpackage.
 
> 
> > Huh?  You're on crack.  Of course you can have multiple packages of
> > different versions installed at the same time.  Just "rpm -i <pkg>"
> > and you've now got two versions installed.
> 
> I may be on crack, but that's a different issue. 
> 
> You can have multiple versions of the same package installed -- but you
> still can't have multiple *subpackages* (in a spec file) with the same name
> but different versions. But if you're intending to separate out the kernel
> module into a completely separate source RPM, that isn't relevant.
> 

My 2.4 RPMs allow me to install as many of the openafs-kernel
subpackages as I need to.  RPM really treats them as normal packages,
its just they way they are built that make them "subpackages."

Granted, for each "version" of openafs-kernel I have installed,
somewhere I've had to built the entire set of openafs packages with that
version.  Many of my RHEL machines look like this:

pams% rpm -qa|grep openafs
openafs-devel-1.2.11-9.EL
openafs-kernel-1.2.11-6.EL
openafs-1.2.11-9.EL
openafs-kernel-1.2.11-10.EL
openafs-kernel-1.2.11-8.EL
openafs-kernel-1.2.11-9.EL
openafs-client-1.2.11-9.EL


> > Also, the plan was to have:
> > openafs-kernel-<openafs-version>-<kernel-version>.<arch>.rpm
> 
> Or openafs-kernel-<openafs-version>-<pkg.release>.<kernel-version>.<arch>.rpm.
> 
> 
> -- 
> Matthew Miller           mattdm@mattdm.org        <http://www.mattdm.org/>
> Boston University Linux      ------>                <http://linux.bu.edu/>
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
> 

-- 
Jack Neely <slack@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