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

api: `purge_packages" don't autoremove on updates #2622

Merged
merged 2 commits into from
Jul 19, 2024
Merged

Conversation

theofficialgman
Copy link
Collaborator

No description provided.

@Botspot Botspot merged commit 5f95b7d into master Jul 19, 2024
3 checks passed
@Botspot Botspot deleted the fast-update branch July 19, 2024 17:51
api
@@ -734,7 +734,7 @@ purge_packages() { #Allow dependencies of the $app app to be autoremoved.

status "Purging the $package_name package..."

if [[ "$script_input" == "update" ]]; then
if [ "$script_input" == "update" ]; then
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

api has #!/bin/bash which guarantees bash (or equivalent implementation) execution

the use of double brackets is common in the api script. Even though there is no wildcard pattern matching being done (which would require double brackets) I see no reason why not to just use double brackets exclusively

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will admit it is a very unimportant design preference of mine, but the way I learned bash gradually through online searches, double brackets mean regex.
Whenever I see double brackets I'm expecting to see regex, and when it's not there I end up re-reading the expression multiple times to check if I am missing any * characters.

Because you brought it up, I will try to drop the habit, but no promises on a timeline for that. :)

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

Successfully merging this pull request may close these issues.

2 participants