Packaging: add dep on crudini & regenerate lockfiles/st2.lock #6329
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is working towards doing packaging via pantsbuild. Eventually, I hope to archive and stop using st2-packages.git.
This PR does 3 things:
crudini
pex_binary
target meant to be used when packaging deb/rpm with pants.lockfiles/st2.lock
to include crudini (it has to be in thest2
resolve because this is a transitive dep of the deb/rpm package targets).lockfiles/st2.lock
to the legacy requirements files.In a follow-up PR (#6330 is a draft), I will add some
shell_command
targets that modify the in-repo conf files during packaging. Currently st2-packages does this withsed
, but it uses features that are only available in gnu sed, making it not very portable. Anyone that tried to run the sed commands on Mac--which would probably only happen during local development--the sed commands would fail. Crudini, on the other hand, is very portable and system agnostic. Plus, st2-packages.git uses crudini for several other things. So, crudini seems like a good way to edit the conf files on the fly without the portability concerns.crudini
will not end up in the final st2 venv because we don't transitively depend on it from our code. We can explicitly include it later if that is helpful.Crudini links: