Charlie Marsh 07e3694c3c Separate local archive vs. local source tree paths in source database (#2922) ... ## Summary When you specify a source distribution via a path, it can either be a path to an archive (like a `.tar.gz` file), or a source tree (a directory). Right now, we handle both paths through the same methods in the source database. This PR splits them up into separate handlers. This will make hash generation a little easier, since we need to generate hashes for archives, but _can't_ generate hashes for source trees. It also means that we can now store the unzipped source distribution in the cache (in the case of archives), and avoid unzipping the source distribution needlessly on every invocation; and, overall, let's un enforce clearer expectations between the two routes (e.g., what errors are possible vs. not), at the cost of duplicating some code. Closes #2760 (incidentally -- not exactly the motivation for the change, but it did accomplish it).		2024-04-09 01:12:33 +00:00
..
src	Separate local archive vs. local source tree paths in source database (#2922)	2024-04-09 01:12:33 +00:00
Cargo.toml	Add an in-memory cache for Git references (#2682)	2024-03-27 01:39:01 +00:00