Hello!
I'm a Sysadmin at a college that uses OpenAFS.  I maintain our Redhat
Satellite server, which can be set up to mirror external yum repositories.
Generally that's what I do with other 3rd party packages such as Adobe or
Puppetlabs.  Those providers provide a yum repo path along the lines of:
/distro/os-major-release/arch/latest
-or-
/distro/os-major-release/arch/product-major-release/latest
...which I can define once and use forever for the latest release of a
product or a product major release version.  This is very useful to me as
it takes the pressure of watching for new minor releases to be released,
then redefining my repository sync configuration each time the path changes
to a new minor release.

Is this something that the OpenAFS folks might consider adopting?

Thanks,
 - Kodiak Firesmith

Reply via email to