On 1 July 2015 at 22:33, Schalk Cronjé wrote:
> VFS correctly depends on Compress as it uses the Tar etc. libraries from
> there.
>
> What I was referring to is backporting the provider code to VFS. The
> provider relies on the CPIO code from Compress,
I see, sorry for the noise.
If there is int
VFS correctly depends on Compress as it uses the Tar etc. libraries from
there.
What I was referring to is backporting the provider code to VFS. The
provider relies on the CPIO code from Compress,
On 01/07/2015 22:01, sebb wrote:
Commons Compress already supports CPIO.
Perhaps that needs ex
Commons Compress already supports CPIO.
Perhaps that needs extending to fit better with VFS, but it seems
wrong to put the CPIO code in VFS which already depends on Compress.
On 1 July 2015 at 21:25, Schalk Cronjé wrote:
> Would anyone fancy backporting this cpio-provider
> (https://github.com/y
Would anyone fancy backporting this cpio-provider
(https://github.com/ysb33r/groovy-vfs/tree/development/cpio-provider)
into Java and adding it to VFS?
I pretty much wrote it based upon the Tar provider.
--
Schalk W. Cronjé
Twitter / Ello / Toeter : @ysb33r
-
