can i tell caxa where it extracts itself too?

[divramod]

hey @leafac,

i am using a cli, build with caxa, in a cicd pipeline.
it would be perfect for me to be able to tell caxa, where to selfextract, so that the archive doesn't need to selfextract every time in a new step (new docker image run).

currently every time i run a cli command, caxa has the initial overload of the self extracting process.

are there any ideas, on how i could solve this?

thx for the awesome tool!

[leafac]

Hi @divramod,

Thanks for considering using caxa.

I’ve been thinking about the broad strategy employed by caxa and concluded that there is a better way to solve the problem. It doesn’t include a self-extracting executable at all, so what you’re reporting is no longer an issue.

It’s a different enough approach that I think it deserves a new name, and it’s part of a bigger toolset that I’m building, which I call Radically Straightforward · Package.

I’m deprecating caxa and archiving this repository. I invite you to continue the conversation in Radically Straightforward’s issues.

Best.