starred/sharpcompress
1
0
Fork 0
mirror of https://github.com/adamhathcock/sharpcompress.git synced 2026-02-13 13:35:28 +00:00
Code Issues 975 Packages Projects Releases 23 Wiki Activity

Adding a Hard Link entry type for Tar #81

New Issue
Open
opened 2026-01-29 22:06:16 +00:00 by claunia · 3 comments
claunia commented 2026-01-29 22:06:16 +00:00
Owner
Copy Link

Originally created by @maygarg on GitHub (Feb 2, 2016).

Hi,

I need to be able to add Hard Link entries in a Tar Archive.

In the current code TarEntry has a TarFilePart, TarFilePart has a TarHeader, TarHeader has an EntryType property where probably a HardLink type can be specified but TarFilePart, TarHeader and EntryType are all inaccessible from the client code.

Even if they were, there is no property which will have the Link file name.

Am I missing anything here or the SharpCompress library does not support writing Hard Link entries to a Tar archive?

Regards,
Mayank

Originally created by @maygarg on GitHub (Feb 2, 2016). Hi, I need to be able to add Hard Link entries in a Tar Archive. In the current code TarEntry has a TarFilePart, TarFilePart has a TarHeader, TarHeader has an EntryType property where probably a HardLink type can be specified but TarFilePart, TarHeader and EntryType are all inaccessible from the client code. Even if they were, there is no property which will have the Link file name. Am I missing anything here or the SharpCompress library does not support writing Hard Link entries to a Tar archive? Regards, Mayank
claunia commented 2026-01-29 22:06:16 +00:00
Author
Owner
Copy Link

@adamhathcock commented on GitHub (Feb 3, 2016):

I'll have to revisit the Tar code. I can't remember I properly implemented Hard Links or not. I do know Tar is one of the more incomplete implementations in sharpcompress.

@adamhathcock commented on GitHub (Feb 3, 2016): I'll have to revisit the Tar code. I can't remember I properly implemented Hard Links or not. I do know Tar is one of the more incomplete implementations in sharpcompress.
claunia commented 2026-01-29 22:06:17 +00:00
Author
Owner
Copy Link

@konste commented on GitHub (Aug 11, 2016):

Is there a chance you may revisit this issue? Storing Hardlinks in TAR is its unique feature and the reason may people actually select TAR over other archivers - it makes dramatic difference when the data contain many duplicate files.

@konste commented on GitHub (Aug 11, 2016): Is there a chance you may revisit this issue? Storing Hardlinks in TAR is its unique feature and the reason may people actually select TAR over other archivers - it makes dramatic difference when the data contain many duplicate files.
claunia commented 2026-01-29 22:06:17 +00:00
Author
Owner
Copy Link

@adamhathcock commented on GitHub (Aug 11, 2016):

It is unlikely I'll be doing anything with sharpcompress myself between a young family and work.

Accepting pull requests though!

@adamhathcock commented on GitHub (Aug 11, 2016): It is unlikely I'll be doing anything with sharpcompress myself between a young family and work. Accepting pull requests though!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
duplicate
enhancement
feedback requested
not bug
pull-request
Mirrored from GitHub Pull Request
 question
up for grabs
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/sharpcompress#81
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?