[elrepo-devel] OpenAFS

[Phil Perry]

On 11/01/11 21:15, Jack Neely wrote:
> On Tue, Jan 11, 2011 at 11:41:15AM -0800, Akemi Yagi wrote:
>> On Tue, Jan 11, 2011 at 11:14 AM, Jack Neely<jjneely at ncsu.edu>  wrote:
>>> Folks,
>>>
>>> I'd like to contribute my OpenAFS packages to ELRepo.  OpenAFS is a
>>> network file system that offers "federated file sharing and replicated
>>> read-only content distribution, providing location independence,
>>> scalability, security, and transparent migration capabilities."  Its
>>> used by many universities and at, at least, one large banking
>>> institution.
>>>
>>> I've built the following packages using the kmodspec and kmodtool
>>> templates from the website.  These are the same packages I'm using
>>> currently in my RHEL 6 deployment.
>>>
>>> SRPMS:
>>>
>>>     http://www4.ncsu.edu/~jjneely/SRPMS/openafs-1.4.14-1.el6.src.rpm
>>>     http://www4.ncsu.edu/~jjneely/SRPMS/openafs-kmod-1.4.14-1.el6.src.rpm
>>>
>>> SPCES:
>>>
>>>     http://www4.ncsu.edu/~jjneely/SPECS/openafs-1.4.14-1.el6.spec
>>>     http://www4.ncsu.edu/~jjneely/SPECS/openafs-kmod-1.4.14-1.el6.spec
>>>
>>> I don't currently use ELRepo style packages for RHEL 5, but if the above
>>> are acceptable I'd be glad to build those as well.
>>>
>>> Thanks,
>>> Jack Neely
>>
>> Hi Jack,
>>
>> Thanks for your offer to contribute openafs. It is definitely
>> something that will be useful to RHEL (and its clones) users. I know
>> Scientific Linux has been offering it for some time.
>>
>> Now, I believe that none of us ELRepo team members are using (or
>> familiar with) openafs -- please correct me if I'm wrong.  So, it is
>> important that we have someone, or a group of people, who can
>> maintain, troubleshoot, and provide some form of support. Do you think
>> you can act as a maintainer of the ELRepo openafs packages?  Or is
>> there anyone on this list who can volunteer to help?
>>
>
> Being the maintainer of these packages isn't a problem.  Just let me
> know how to get things done.
>
> Jack
>

Hi Jack,

Thanks for the contribution.

Probably the easiest way to maintain the packages is to submit updated 
spec and/or SRPM files as required and someone here can build and push 
them for you. However, if you'd like to be more involved, we have a 
public build system and can grant you build access to build your own 
packages, but someone would still need to sign and push the built 
packages. So whichever works best for you.

Regards,

Phil