Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

compressed output #171

Open
nsheff opened this issue Mar 5, 2020 · 0 comments
Open

compressed output #171

nsheff opened this issue Mar 5, 2020 · 0 comments

Comments

@nsheff
Copy link
Member

nsheff commented Mar 5, 2020

maybe there's a compress_add() function. then, the clean step will compress these (using some provided function, maybe pigz by default).

if a target is given that is in the compress list, and the compressed file exists, instead of repeating, it will just decompress the file.

running in 'dirty' mode would not compress the files.
or maybe there's a new mode for 'compress' but don't delete.

ok here we go:

--clean and --compress both default to 1.
You can set: --clean 0 to NOT clean. you can set --compress 0 to NOT compress.
You can also set --clean 2 to clean extra; same for compressing.

If the pipeline author would use:

pm.clean_add(file, 1) that puts it at the default clean level. for level 2, it would be pm.clean_add(file, 2). The default is 1 so it's backwards compatible and you can still do clean.add(file).`
The same idioms would be used for compress.

question: what about cleaning a compressed file? like, it's compress level 1, and clean level 2? So you may want it compressed, or maybe deleted?

in that case, maybe clean runs first so we don't compress something we're going to just delete anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant