Change Details

(proposal) I had to open some more methods (download, uncompress, read_intrinsic_metadata) Contrary to other package loaders, all artifacts (for a version) are ingested as one revision. Not implemented: - no optimization about reading the snapshot yet (I'd like to make sure we agree first ;) We'll need to adapt slightly the debian lister to pass solely the origin url and not the origin dict (D2137, D2138). Note: This does not use `swh.storage.schemata` (which is not a problem as long as we implement the snapshot reading optimization ;) Related T2025 Related D2133 Related D2134

(proposal) I had to open some more methods (download, uncompress, read_intrinsic_metadata) Contrary to other package loaders, all artifacts (for a version) are ingested as one revision. There is no optimization about reading the snapshot yet (-> D2142) We'll need to adapt slightly the debian lister to pass solely the origin url and not the origin dict (D2137, D2138). Note: This does not use `swh.storage.schemata` so when this lands, this can move back to the lister stack (that's the lister's model initialization or even be dropped altogether...) Related T2025 Related D2133 Related D2134

(proposal) I had to open some more methods (download, uncompress, read_intrinsic_metadata) Contrary to other package loaders, all artifacts (for a version) are ingested as one revision. Not implemented: -There is no optimization about reading the snapshot yet (I'd like to make sure we agree first ;-> D2142) We'll need to adapt slightly the debian lister to pass solely the origin url and not the origin dict (D2137, D2138). Note: This does not use `swh.storage.schemata` (which is not a problem as long as we implement the snapshot reading optimization ;so when this lands, this can move back to the lister stack (that's the lister's model initialization or even be dropped altogether...) Related T2025 Related D2133 Related D2134