-
Notifications
You must be signed in to change notification settings - Fork 15
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
Stored commands #7
Comments
Are you suggesting creating a way for a user to store their own personally-used commands? If you mean the first, can you explain why this would be preferable to modifying one's bash_profile (or the equivalent for their environment)? |
Actually, neither of those. I was hoping to have shared groups of commands. e.g. dos2unix = ...
fix_hashbang = ...
remove_hashbang = ... Then that command list could be put into a package , which would be installed into the rpmbuild environment, or installed by packagers locally for debugging, and used something like The reason for having multiple alias files is to allow different rpms to 'own' different sets of alias files, to prevent conflicts in rpm packaging. |
In packaging .spec files, there are a few very common tasks which are normally done with sed/awk/etc.
Most could be expressed as a bsed command which would be nice.
e.g. equiv of dos2unix, removing hashbang, replacing hashbangs.
i.e. https://python-rpm-porting.readthedocs.io/en/latest/applications.html#fixing-shebangs really recommends people write those commands. Surely we can do better than that before 2020 lands ;-)
Packaging python has a few others like replace == with >= inside setup.py strings.
It would be useful if these could be stored commands somehow.
they could be scripts which use bsed as their interpreter, or named aliases like 'bsed run foo', with details in a config.
The text was updated successfully, but these errors were encountered: