On 12/4/18 1:09 PM, Eli Schwartz wrote:
> Whenever adding new package files to the pool of distributed packages,
> hardlink a copy of every package it was built with, into a
> "reproducible" pool, and log which file required it.
The question becomes, where can I store these? As-is, this will
This is never ever called for multiple packages at once, and if it was,
it would be named clean_pkgs. Meanwhile, it was implied that this could
take a variable target, but that was never-used code. Make it useful
because we might (will) use it.
Signed-off-by: Eli Schwartz
---
Whenever adding new package files to the pool of distributed packages,
hardlink a copy of every package it was built with, into a
"reproducible" pool, and log which file required it.
Signed-off-by: Eli Schwartz
---
config | 1 +
config.local.svn-community | 1 +
This reuses the same logic used for normally deleting packages, but
cleanup of the reproducible archive happens in a subdirectory of
${CLEANUP_DESTDIR} while still subject to the same timeouts.
Signed-off-by: Eli Schwartz
---
cron-jobs/ftpdir-cleanup | 18 ++
1 file changed, 14
Prerequisite for reproducible archives of packages.
Signed-off-by: Eli Schwartz
---
test/lib/common.bash | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/test/lib/common.bash b/test/lib/common.bash
index bc2b4e6d..3dda5f62 100644
--- a/test/lib/common.bash
+++
