Re: commons compress status?

2007-05-19 Thread Torsten Curdt
On 18.05.2007, at 19:17, Bear Giles wrote: Torsten Curdt wrote: Hm... seems like I disagree here. I want a simple library that deals with common compression and archive formats - tar - ar - cpio - gzip - bzip2 - zip VFS is a filesystem abstraction layer. It may use the library

Re: commons compress status?

2007-05-18 Thread Bear Giles
Torsten Curdt wrote: Hm... seems like I disagree here. I want a simple library that deals with common compression and archive formats - tar - ar - cpio - gzip - bzip2 - zip VFS is a filesystem abstraction layer. It may use the library but should not provide the implementation IMO. C

Re: commons compress status?

2007-05-18 Thread Jochen Wiedmann
On 5/18/07, Torsten Curdt <[EMAIL PROTECTED]> wrote: VFS is a filesystem abstraction layer. It may use the library but should not provide the implementation IMO. +1, compression is a rather important topic in itself. -- My cats know that I am a loser who goes out for hunting every day wi

Re: commons compress status?

2007-05-18 Thread Torsten Curdt
On 18.05.2007, at 05:13, Bear Giles wrote: Thorbjørn Ravn Andersen wrote: I therefore suggest that the tar methods should be migrated to the vfs module (if suitable) and that the compress module should contain methods that can compress/uncompress streams (which is easily extendable to fil

Re: commons compress status?

2007-05-17 Thread Mario Ivankovits
Hi! > I agree that the 'compress' tar classes should be removed and a > pointer left to the VFS project. We've already moved an early version (before the api cleanup) of the COMPRESS codebase to VFS. The thing is, that VFS normally would NOT like to provide the implementation for a certain filesys

Re: commons compress status?

2007-05-17 Thread Bear Giles
Thorbjørn Ravn Andersen wrote: I therefore suggest that the tar methods should be migrated to the vfs module (if suitable) and that the compress module should contain methods that can compress/uncompress streams (which is easily extendable to files, http connections etc). By doing so there wi

Re: commons compress status?

2007-05-17 Thread Thorbjørn Ravn Andersen
[EMAIL PROTECTED] skrev den 17-05-2007 00:20: You can't do that if you only see archives as boring things used in backups. Backups that are either windows (zip) or unix (tar), yawn. If you go hardcore, you'll notice that a lot of common file formats provide support for arbitrary data to be bu

Re: commons compress status?

2007-05-16 Thread Henri Yandell
On 5/16/07, Bear Giles <[EMAIL PROTECTED]> wrote: Torsten Curdt wrote: > On 15.05.2007, at 23:29, [EMAIL PROTECTED] wrote: > >> I'm interested in merging some earlier archival work (in C) into commons >> compress and would like to know who to coordinate with. The changes >> will >> be... substa

Re: commons compress status?

2007-05-16 Thread Bear Giles
Torsten Curdt wrote: On 15.05.2007, at 23:29, [EMAIL PROTECTED] wrote: I'm interested in merging some earlier archival work (in C) into commons compress and would like to know who to coordinate with. The changes will be... substantial... and I'll probably just fork the project for now, with

Re: commons compress status?

2007-05-16 Thread Torsten Curdt
On 15.05.2007, at 23:29, [EMAIL PROTECTED] wrote: I'm interested in merging some earlier archival work (in C) into commons compress and would like to know who to coordinate with. The changes will be... substantial... and I'll probably just fork the project for now, with a goal of merging

Re: commons compress status?

2007-05-16 Thread bgiles
> On 5/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> I'm interested in merging some earlier archival work (in C) into commons >> compress and would like to know who to coordinate with. The changes >> will >> be... substantial... and I'll probably just fork the project for now, >> with >>

Re: commons compress status?

2007-05-16 Thread Henri Yandell
On 5/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: I'm interested in merging some earlier archival work (in C) into commons compress and would like to know who to coordinate with. The changes will be... substantial... and I'll probably just fork the project for now, with a goal of merging

commons compress status?

2007-05-15 Thread bgiles
I'm interested in merging some earlier archival work (in C) into commons compress and would like to know who to coordinate with. The changes will be... substantial... and I'll probably just fork the project for now, with a goal of merging in late summer. Also, what version of the JDK do projects

Re: [compress] Status

2006-07-24 Thread C. Grobmeier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Niall Pemberton wrote: > Slightly OT for this thread, but compress now has a nightly build: > http://people.apache.org/builds/jakarta-commons/nightly/commons-compress/ That's great :-) > Will email my fax number to Torsten/Chris and see if I can a) r

Re: Re: [compress] Status

2006-07-24 Thread Niall Pemberton
Slightly OT for this thread, but compress now has a nightly build: http://people.apache.org/builds/jakarta-commons/nightly/commons-compress/ Niall On 7/24/06, Henri Yandell <[EMAIL PROTECTED]> wrote: On 7/19/06, Henri Yandell <[EMAIL PROTECTED]> wrote: > On 7/18/06, Torsten Curdt <[EMAIL PROTEC

Re: Re: [compress] Status

2006-07-23 Thread Henri Yandell
On 7/19/06, Henri Yandell <[EMAIL PROTECTED]> wrote: On 7/18/06, Torsten Curdt <[EMAIL PROTECTED]> wrote: > > It's high time we just committed these changes and moved on from there, > > I think. > > Yepp! That was what Mario I thought, too ...we are only waiting for > Jim to acknowledge the softw

Re: Re: [compress] Status

2006-07-19 Thread Henri Yandell
On 7/18/06, Torsten Curdt <[EMAIL PROTECTED]> wrote: > It's high time we just committed these changes and moved on from there, > I think. Yepp! That was what Mario I thought, too ...we are only waiting for Jim to acknowledge the software grant. (*sigh*) Gotya, which hasn't been received yet.

Re: [compress] Status

2006-07-18 Thread C. Grobmeier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Chris - do you have any more recent changes or should we go with draft 8? I think it's better now to commit and let others participate. I have no recent changes and would like to wait till the code is in the repos. Regards, Chris -BEGIN PGP SIG

Re: Re: [compress] Status

2006-07-18 Thread Torsten Curdt
It's high time we just committed these changes and moved on from there, I think. Yepp! That was what Mario I thought, too ...we are only waiting for Jim to acknowledge the software grant. (*sigh*) cheers -- Torsten - To unsubs

Re: [compress] Status

2006-07-18 Thread Brett Porter
About a month ago there was a new draft posted, and Mario had some comments which Chris said he'd take into consideration. It's high time we just committed these changes and moved on from there, I think. Chris - do you have any more recent changes or should we go with draft 8? - Brett On 19

[compress] Status

2006-07-18 Thread Henri Yandell
What's the status of compress? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]