Uploaded image for project: 'Commons Compress'
  1. Commons Compress
  2. COMPRESS-182

Support big or even negative numbers in all numeric TAR headers

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.3
    • Fix Version/s: 1.4
    • Component/s: Archivers
    • Labels:
      None

      Description

      This is a superset of the functionality that addressed COMPRESS-175

      Jörg Schillig's star and GNU tar may use binary encoding for all numeric fields, PAX/POSIX also provides them inside the extension headers.

      The timestamp field may even contain negative numbers.

      IMHO Commons Compress should:

      • be able to parse numeric fields using binary encoding (positive and negative)
      • fix the current binary parser (see discussion in COMPRESS-16) and add a workaround for broken writers (see COMPRESS-181)
      • be able to parse all standard fields of PAX headers, including the numeric ones (I haven't checked, maybe it already does)
      • have an option to write numbers too big/small in binary encoding much like BIGFILE_STAR does for the file size in trunk
      • have an option to write numbers too big/small in PAX headers much like BIGFILE_POSIX does for the file size in trunk
      • replace bigFileMode and the constants with a more generic property that controls all numeric fields. We can remove the bigFileMode stuff as it has been added after the 1.3 release.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                bodewig Stefan Bodewig
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: