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

Add --pacman-cache, --pacman-log and --maxdepth to CLI options #123

Merged
merged 5 commits into from May 11, 2020

Conversation

atreyasha
Copy link
Member

@atreyasha atreyasha commented May 10, 2020

This PR addresses #120 by adding --pacman-cache, --pacman-log and --maxdepth as CLI options. Commits have been chunked to represent discrete components of this PR.

Regarding whether to include --maxdepth at all, I think it is a good idea to include this parameter to ensure that find does not get stuck searching some deep user-defined cache directory. The user can add an arbitrarily large value for this if they want to search some basic cache directory for (eg.) AUR packages.

Copy link
Member

@pbrisbin pbrisbin left a comment

Choose a reason for hiding this comment

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

Good to merge once you rename MAXDEPTH.

downgrade Outdated Show resolved Hide resolved
downgrade Outdated Show resolved Hide resolved
doc/downgrade.8.md Outdated Show resolved Hide resolved
doc/downgrade.8.md Outdated Show resolved Hide resolved
completion/zsh Outdated Show resolved Hide resolved
@atreyasha
Copy link
Member Author

Made the respective fixes. Removed the commits for the man-doc to prevent conflicts. I had to keep the changes to the locale since I added translations for new keys. If all is fine, you can merge it.

@atreyasha atreyasha requested a review from pbrisbin May 11, 2020 15:40
@atreyasha atreyasha force-pushed the as/log-cache-maxdepth-cli branch 2 times, most recently from 3abd087 to 9e8e31c Compare May 11, 2020 16:52
@atreyasha
Copy link
Member Author

atreyasha commented May 11, 2020

Is it okay if I do the merging to master (for both PRs) and fixing of the conflicts directly in master?

@pbrisbin
Copy link
Member

I do the merging to master (for both PRs) and fixing of the conflicts directly in master?

You should be able to,

  • Merge one of them (GitHub UI shows no conflicts)
  • Rebase the other one, fix conflicts
  • Merge the other one

I don't think anything should need fixing "in master", right?

@atreyasha
Copy link
Member Author

Ah sorry I worded that wrongly, there should be no conflicts in master itself. There will probably be some conflicts before the merge but I can fix those in the UI directly. Will do it then.

@atreyasha atreyasha force-pushed the as/log-cache-maxdepth-cli branch 2 times, most recently from 4890f44 to 5bbf7f5 Compare May 11, 2020 17:58
@atreyasha atreyasha merged commit 96b67a7 into master May 11, 2020
@atreyasha atreyasha deleted the as/log-cache-maxdepth-cli branch May 11, 2020 18:01
@atreyasha
Copy link
Member Author

Merging done for both. Just need to rebuild the man-page/changelog which I will leave to you.

@pbrisbin
Copy link
Member

And just double-checking, major version bump because we changed how = works?

@atreyasha
Copy link
Member Author

Yes major version bump sounds right.

@pbrisbin
Copy link
Member

🎉 8.0.0 released

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.

Creating --pacman-log, --pacman-cache and --maxdepth command-line arguments
2 participants