On Fri, Jul 26, 2013 at 2:29 AM, Bryan Berry email@example.com wrote:
Some time ago, I created the ark LWRP to handle the unpack, configure, link,
install dance. I was never quite happy with it, primarily because it
conflated two separate concerns that are best handled by diffferent LWRPS,
- getting a tarball and 2) configuring its contents along the
configure-make-symlink lines. I have written a new LWRP for doing the
download part and I hope I get the chance to open-source it some time soon.
Just as a heads up I started down the same path with  and have
started using it fairly extensively on both windows and linux. I did
run into a few issues with regards to symlinks under windows as the
builtin link resource does not work on windows when the target is
Other than that I am fairly happily using it to do versioned archive
downloads on multiple platforms. On both platforms I tend to have
downstream build steps that use notifications.
One of the pain points was different applications requiring/wanting
different layouts. Although it has yet to be fully merged upstream I
ended up going down the path of having to support multiple strategies
for dealing with different layouts. From memory, some of the
strategies looked like
/usr/local/foo -> /usr/local/foo-2.3
/usr/local/foo/versions/current -> /usr/local/foo/versions/2.3
/usr/local/foo/cur -> /usr/local/foo/2.3
Anyhoo I would e very interested in seeing what you have come up with.
As the work on archive was initially inspired by ark