mirrors/tar-split
1
0
Fork 1
mirror of https://github.com/vbatts/tar-split.git synced 2024-11-22 08:05:39 +00:00
Code Releases Activity
tar-split/go.mod

23 lines
618 B
Modula-2
Raw Normal View History

go mod closer coupling to versions of depencies Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2020-10-27 16:09:19 +00:00
module github.com/vbatts/tar-split
*: mage, drop go1.1{5,6}, module updates, drop vendor Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2023-03-26 18:01:33 +00:00
go 1.17
*go: update all modules to the latest still compatible with go1.15 Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2023-03-26 02:20:56 +00:00
go mod closer coupling to versions of depencies Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2020-10-27 16:09:19 +00:00
require (
*: mage, drop go1.1{5,6}, module updates, drop vendor Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2023-03-26 18:01:33 +00:00
github.com/fatih/color v1.15.0
github.com/magefile/mage v1.14.0
go*: update modules Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2024-09-26 23:51:49 +00:00
github.com/sirupsen/logrus v1.9.3
Add tar/asm.IterateHeaders This allows reading the metadata contained in tar-split without expensively recreating the whole tar stream including full contents. We have two use cases for this: - In a situation where tar-split is distributed along with a separate metadata stream, ensuring that the two are exactly consistent - Reading the tar headers allows making a ~cheap check of consistency of on-disk layers, just checking that the files exist in expected sizes, without reading the full contents. This can be implemented outside of this repo, but it's not ideal: - The function necessarily hard-codes some assumptions about how tar-split determines the boundaries of SegmentType/FileType entries (or, indeed, whether it uses FileType entries at all). That's best maintained directly beside the code that creates this. - The ExpectedPadding() value is not currently exported, so the consumer would have to heuristically guess where the padding ends. Signed-off-by: Miloslav Trmač <mitr@redhat.com>
2024-09-11 17:54:20 +00:00
github.com/stretchr/testify v1.9.0
go*: update modules Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2024-10-21 14:33:58 +00:00
github.com/urfave/cli v1.22.16
go mod closer coupling to versions of depencies Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2020-10-27 16:09:19 +00:00
)
*: mage, drop go1.1{5,6}, module updates, drop vendor Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2023-03-26 18:01:33 +00:00
require (
go*: update modules Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2024-09-26 23:51:49 +00:00
github.com/cpuguy83/go-md2man/v2 v2.0.5 // indirect
Add tar/asm.IterateHeaders This allows reading the metadata contained in tar-split without expensively recreating the whole tar stream including full contents. We have two use cases for this: - In a situation where tar-split is distributed along with a separate metadata stream, ensuring that the two are exactly consistent - Reading the tar headers allows making a ~cheap check of consistency of on-disk layers, just checking that the files exist in expected sizes, without reading the full contents. This can be implemented outside of this repo, but it's not ideal: - The function necessarily hard-codes some assumptions about how tar-split determines the boundaries of SegmentType/FileType entries (or, indeed, whether it uses FileType entries at all). That's best maintained directly beside the code that creates this. - The ExpectedPadding() value is not currently exported, so the consumer would have to heuristically guess where the padding ends. Signed-off-by: Miloslav Trmač <mitr@redhat.com>
2024-09-11 17:54:20 +00:00
github.com/davecgh/go-spew v1.1.1 // indirect
*: mage, drop go1.1{5,6}, module updates, drop vendor Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2023-03-26 18:01:33 +00:00
github.com/mattn/go-colorable v0.1.13 // indirect
github.com/mattn/go-isatty v0.0.17 // indirect
Add tar/asm.IterateHeaders This allows reading the metadata contained in tar-split without expensively recreating the whole tar stream including full contents. We have two use cases for this: - In a situation where tar-split is distributed along with a separate metadata stream, ensuring that the two are exactly consistent - Reading the tar headers allows making a ~cheap check of consistency of on-disk layers, just checking that the files exist in expected sizes, without reading the full contents. This can be implemented outside of this repo, but it's not ideal: - The function necessarily hard-codes some assumptions about how tar-split determines the boundaries of SegmentType/FileType entries (or, indeed, whether it uses FileType entries at all). That's best maintained directly beside the code that creates this. - The ExpectedPadding() value is not currently exported, so the consumer would have to heuristically guess where the padding ends. Signed-off-by: Miloslav Trmač <mitr@redhat.com>
2024-09-11 17:54:20 +00:00
github.com/pmezard/go-difflib v1.0.0 // indirect
*: mage, drop go1.1{5,6}, module updates, drop vendor Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2023-03-26 18:01:33 +00:00
github.com/russross/blackfriday/v2 v2.1.0 // indirect
go*: update modules Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2024-10-21 14:33:58 +00:00
golang.org/x/sys v0.26.0 // indirect
Add tar/asm.IterateHeaders This allows reading the metadata contained in tar-split without expensively recreating the whole tar stream including full contents. We have two use cases for this: - In a situation where tar-split is distributed along with a separate metadata stream, ensuring that the two are exactly consistent - Reading the tar headers allows making a ~cheap check of consistency of on-disk layers, just checking that the files exist in expected sizes, without reading the full contents. This can be implemented outside of this repo, but it's not ideal: - The function necessarily hard-codes some assumptions about how tar-split determines the boundaries of SegmentType/FileType entries (or, indeed, whether it uses FileType entries at all). That's best maintained directly beside the code that creates this. - The ExpectedPadding() value is not currently exported, so the consumer would have to heuristically guess where the padding ends. Signed-off-by: Miloslav Trmač <mitr@redhat.com>
2024-09-11 17:54:20 +00:00
gopkg.in/yaml.v3 v3.0.1 // indirect
*: mage, drop go1.1{5,6}, module updates, drop vendor Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2023-03-26 18:01:33 +00:00
)
Copy permalink