glusterfs rename

Kaleb S. KEITHLEY kkeithle at
Wed May 30 17:08:03 UTC 2012

On 05/30/2012 12:44 PM, Richard W.M. Jones wrote:
> To be honest it's a pain in the neck to deal with such packages, and
> unless there's an overwhelming need, I can't recommend it.  Does any
> user really need to parallel install both versions of glusterfs?

No, and in fact that would not work. (And it's not the problem we're 
trying to solve.)

If glusterfs-3.2.x + HekaFS is installed, we essentially want to avoid 
ever updating to glusterfs-3.3.x because HekaFS is not compatible with it.

One way I can solve this is to never ship glusterfs-3.3.x on f16 and f17 
(and EPEL el6).

I'd be perfectly happy saying we will never ship glusterfs-3.3.x on f16 
and f17, but the reality is that there probably are people who want it.

Along the same lines, I'd be happy saying we will not ship HekaFS in f18 
once glusterfs-3.3.x is out, but there are probably people who want 
glusterfs-3.2.x, with or without HekaFS.

And FWIW, doing nothing doesn't resolve the glusterfs in EPEL versus 
glusterfs in the RHS Channel issue.



More information about the devel mailing list