-
4e3f5e44 · feat: Add `alpm-package` crate for creating package files from input
- ... and 4 more commits. Compare e44da3d1...4e3f5e44
-
e44da3d1 · feat: Add `alpm-package` crate for creating package files from input
- ... and 5 more commits. Compare 4a9d2aef...e44da3d1
-
400f6d1e · feat: Add functions for the creation of ALPM-MTREE files
- ... and 4 more commits. Compare bd6dcf69...400f6d1e
-
44ded2b3 · feat: Add functions to get relative file paths from input dirs
- ... and 1 more commit. Compare 10729ce0...44ded2b3
-
4a9d2aef · feat: Add `alpm-package` crate for creating package files from input
- ... and 1 more commit. Compare 6f9ab212...4a9d2aef
-
bd6dcf69 · feat: Add functions for the creation of ALPM-MTREE files
Ah, right!...
-
6f9ab212 · feat: Add `alpm-package` crate for creating package files from input
- ... and 5 more commits. Compare eb06f9ae...6f9ab212
I will add the CompressionType and PackageFileName types to the package module as well (in an upcoming MR)....
-
03820007 · feat: Add functions for the creation of ALPM-MTREE files
Alright, I have moved the functionality to specific functions, so that they can be exposed top-level as well.
-
671e1e29 · feat: Add functions for the creation of ALPM-MTREE files
- ... and 4 more commits. Compare 412090a4...671e1e29
I like MtreeV1Creator
better than the other one, as Writer is probably more associated with the Write
trait etc....
You know... all_files: true
etc...
Ah yeah, we can just overwrite that one, fair enough!
How can it sound like a boolean value if it is typed?
-
3707de14 · docs(package): Add alpm-local-desc specification
- ... and 1 more commit. Compare c905594c...3707de14
-
8440be88 · feat: Add alpm-soname crate for soname provision/dependency lookup
Ah yes. I forgot to clean this up when moving.
-
10729ce0 · feat: Add functions to get relative file paths from input dirs
- ... and 1 more commit. Compare 4de72148...10729ce0