Skip to content

Work-around tar.TypeGNUSparse #21

Description

@vbatts

Perhaps the best work around here, will be to have an entry type, that is like Segment and File, but stashes the whole raw bytes of a sparse file entry. This could make the tar-data.json substantially larger, but could preserve the integrity of sparse files, rather than inflating them.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions