ID: |
6217
|
Fixed in: |
|
Issue Date: |
2011-08-02 15:06 AEST
|
Owner: | CVS Support
|
Last Modified: | 2014-09-11 10:45 AEST | Reporter: | Arthur Barrett
|
Current Est. | 0.0 hours
| % Complete: | 0.0
|
Status: | NEW /
|
Severity: | enhancement
|
Affected: | 2.8.02
|
Description: | enh: version iso, cab, zip, tar, gz, tgz, jar file elements individually - not as blob
|
Actions:
|
2011-08-02 15:06 AEST by Arthur Barrett - It is very inefficient to store ZIP files in CVS Server.
For a start - the diff algorithm can't really separate out changes well so the
revision deltas end up being quite large, but it's also not possible to 'diff'.
If the server stored these compound formats as individual files then it would
be more efficient.
This is similar to Mac OS X that has 'containers' which are really a directory
and files. Each Mac OS X system has a list of 'extensions' they
become 'containers' like this.
To support Eclipse and other non-CVSNT clients we'd need to handle it all on
the server. So a client would NEVER see the individual files in the ZIP, or be
able to extract individual files, or tag files separately - but the server
would store them that way.
The CVSWRAPPERS could be used to identify these 'types', eg:
*.zip -ky
*.zip -kY
The individual files that make up the zip would be stored using binary/ascii
using the 'normal' cvswrapper rules.
nested ZIP files (or a zip in a jar, or a jar in a zip) would present a
difficult case, because we wouldn't know how to re-construct easily. In this
case -kY would store nested -kY files as -kB, and -ky would store nested -ky
files as -kb. |
|
2013-07-30 15:54 AEST by Arthur Barrett - also include cab files |
|
2014-09-10 19:14 AEST by Arthur Barrett - Add gz and tgz file extensions to the summary line just for easy searching. |
|
2014-09-11 10:45 AEST by Arthur Barrett - Need to probably 'ignore' files that are signed
- does the client need to identify this (because only a windows PC knows what a signed windows file looks
like, ditto mac).
- does the client need to 'tell' the server 'this is a signed file', then the server decide what rule to apply?
- should 'signed file identification and rules' be a separate bug? bug 6789
Also need to store attributes, e.g.:
- compression algorithm / level of original file
- date/time of original 'container file' (CVS will auto store the date/time of each sub-file)
- what about date/time of 'container' sub-folders?
|
|