Hide Forgot
We've decided that upstream glusterfs-hadoop installer needs 1) A more precise README, phrases such as: - "the goal is to create..." - "The tarball is downloaded to one of the cluster nodes or to the user's..." - "The tarball should contain...." Are somewhat confusing. The readme should clarify which tarball is being referenced. Should we reference the tarball at all ? I don't think so. 2) Once the fedora subfolder implementation of rhs-hadoop-install is close to complete, lets delete or deprecate https://github.com/jeffvance/glusterfs-cluster-install entirely to further simplify things.
(In reply to Jay Vyas from comment #0) > We've decided that upstream glusterfs-hadoop installer needs > > 1) A more precise README, phrases such as: > - "the goal is to create..." > - "The tarball is downloaded to one of the cluster nodes or to the > user's..." > - "The tarball should contain...." > > Are somewhat confusing. The readme should clarify which tarball is being > referenced. Should we reference the tarball at all ? I don't think so. I agree here. Basically we need a new README written for the user who just installed the package. So far the README is written for another developer, so besides user centric stuff it also provides introduction to the structure of the git repository, development, packaging and so on (while most of those files are not provided by the package the user will use). To avoid duplication, I guess the README may be splitted into user and devel one, where only the user one will be packaged.
version 0.54 attempts to address this concern.
should be fixed in version 0.62-1
(In reply to Jeff Vance from comment #4) > should be fixed in version 0.62-1 Using rhs-hadoop-install-0_62-1.el6rhs.noarch