Le vendredi 24 mars 2017 à 09:53 -0400, Kaleb S. KEITHLEY a écrit : > On 03/24/2017 09:39 AM, Niels de Vos wrote: > > On Thu, Mar 23, 2017 at 05:29:05PM -0400, Michael Scherer wrote: > >> Another example: > >> pub/gluster/glusterfs has various directory for versions of glusterfs, > >> but also do have libvirt, vagrant and nfs-ganesha, who are not version, > >> and might be rather served from a directory upstream (in fact, > >> nfs-ganesha and glusterfs-coreutils are also on > >> https://download.gluster.org/pub/gluster/ ) > > > > A cleanup is much appreciated! Maybe come up with a proposed directory > > structure and see from there what makes sense to keep or remove? > > > > What does "from a directory upstream" mean? There is no upstream > nfs-ganesha server Indeed, I mean a directory up (ie, from '..'). I will plead jetlag and lack of coffee. > > There are versions of nfs-ganesha, even if there aren't very many, and > thus not to the same level of granularity as gluster. > > And .../pub/gluster/glusterfs/nfs-ganesha is merely a symlink to > .../pub/gluster/nfs-ganesha — just a convenience. There are not two > copies of it. Likewise for -coreutils and the others. > > I'm not opposed reorganizing the directories, but I don't believe > there's really anything wrong with it, per se, the way it is now. Mhh, I didn't see this was symlink, so maybe that's a first issue with my sync script. I will recheck directory on the download server directly and try to give more direct suggestions. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
