-
Notifications
You must be signed in to change notification settings - Fork 1
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
Install packages both from official repo and CCR. #5
Comments
Yes, ccr can, but why? Is there a reason to allow this? |
Why not? we can do it for a old tool but not new tool? :P |
Idk, I'm just not sure what purpose it serves. If you want to install from the repos, why not just use the package manager? I don't think it would make the logic a lot worse though, maybe i'll look into it. |
On Apr 27, 2016 at 21:28, Ryan Shipp wrote:
Most aur-helpers do this as well. I see these {aur,ccr}-helpers as a What if the pkg you want to install is in the repo but you think it is |
Oh yes, just like @Ram-Z says. |
Specific use case report: To ease distro-hopping I wrote a script that automatically detects available package managers and uses the first one it finds for running basic package management tasks (package search/install/remove/upgrade/info). Before However, the only way I could get automatic correct-command-using package installation for Chakra is by rewriting the entire script to push all that logic into the specific command files, turning them into scripts in and of themselves. So far, I have 21 lines somewhat fragile Bash to support chaser (I still haven't figured out a bullet-proof way to test if I'm out of practice with Python, but I might want to try fixing this issue because it looks like the easiest way to fix my script. Mind pointing me to the contribution process for if I do this? |
As title says, we can use ccr to do it, but chaser can't.
The text was updated successfully, but these errors were encountered: