bundle
bundle copied to clipboard
r-lyeh-archived
from wikipedia
MPQs used in Blizzard's games generally contain a game's data files, including graphics, sounds, and level data. The format's capabilities include compression, encryption, file segmentation, extensible file metadata, cryptographic signature and the ability to store multiple versions of the same file for internationalization and platform-specific differences. MPQ archives can use a variety of compression algorithms which may also be combined.
current features:
- archives can use a variety of compression algorithms which may also be combined.
- extensible file metadata
missing:
- encryption
- file segmentation
- cryptographic signature
- file versioning, internationalization/localization, platform specifics
these would are all be nice features. A cryptographic signature is for me one of the most interesting ones. cryptopp?
I think cryptopp exceeds the size of an amalgamated solution. Maybe something smaller like https://github.com/well-typed/libedsign would fit it better.
On the other hand, and to avoid feature creep, I think bundle is ok as a compression library as it is right now. Maybe it could be wiser to add some of these features into another library on top of bundle. In same way than bundler is an archiver on top of bundle: https://github.com/r-lyeh/bundler
Yeah, I agree, there is no need to add features at any cost to an independent component. An encryption/signing can have a similar interface as bundle and thus a component in itself, but usable together with bundle in an aggregating component. As for libedsign, it looks suspicious to me. The crypto textbooks warn against using something that isn't widely used. As for cryptopp, it seems to be quite modular and not that complicated to build, hence a precise selection of it could be amalgamated, perhaps.