@janstey @KurtStam Please take a look...I am copying (rather than symlinking) the "bin", "etc", and "data" directories... are there any other directories you feel should be copied (ie need to be user writeable?) once the fuse patching process is fixed?
I am assuming we can't merge this until the fuse patching is fixed (although if we don't care that patching is broken, we could merge this so QE can get going on it...it does seem to make deployments faster).
Also the rpm spec file needs closer examination... because I was hacking this together it's referencing the "385" version of the zip specifically.......I'm not sure what Matej is doing in general to build the rpms (and I don't know his github id, so feel free to loop him into this PR). It may not even be the best way to accomplish the goals, but unfortunately I am not an RPM expert.
@janstey @KurtStam Please take a look...I am copying (rather than symlinking) the "bin", "etc", and "data" directories... are there any other directories you feel should be copied (ie need to be user writeable?) once the fuse patching process is fixed?
I am assuming we can't merge this until the fuse patching is fixed (although if we don't care that patching is broken, we could merge this so QE can get going on it...it does seem to make deployments faster).
Also the rpm spec file needs closer examination... because I was hacking this together it's referencing the "385" version of the zip specifically.......I'm not sure what Matej is doing in general to build the rpms (and I don't know his github id, so feel free to loop him into this PR). It may not even be the best way to accomplish the goals, but unfortunately I am not an RPM expert.