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

Install packages both from official repo and CCR. #5

Open
s8321414 opened this issue Apr 27, 2016 · 6 comments
Open

Install packages both from official repo and CCR. #5

s8321414 opened this issue Apr 27, 2016 · 6 comments
Milestone

Comments

@s8321414
Copy link

As title says, we can use ccr to do it, but chaser can't.

@rshipp
Copy link
Member

rshipp commented Apr 27, 2016

Yes, ccr can, but why? Is there a reason to allow this?

@s8321414
Copy link
Author

Why not? we can do it for a old tool but not new tool? :P
Though we will go to akabei anyway...

@rshipp
Copy link
Member

rshipp commented Apr 28, 2016

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.

@Ram-Z
Copy link

Ram-Z commented Apr 28, 2016

On Apr 27, 2016 at 21:28, Ryan Shipp wrote:

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.

Most aur-helpers do this as well. I see these {aur,ccr}-helpers as a
superset of pacman. IMHO they should be able to install pacman pkgs as
well.

What if the pkg you want to install is in the repo but you think it is
in CCR? Running chaser and not finding it might make you think the pkg
does not exist.

@s8321414
Copy link
Author

Oh yes, just like @Ram-Z says.

@rshipp rshipp added this to the 1.0 milestone Apr 28, 2016
@refola
Copy link

refola commented Mar 4, 2019

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 chaser was marked as replacing ccr and the latter was dropped from Chakra's repos, I was able to support all distros I've used with simple "run a sequence of commands" logic with automatic use/non-use of sudo as appropriate. Migrating from ccr to chaser, literally everything except package installation worked with the same logic and just needed straightforward translations from ccr commands to chaser commands.

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 pacman has a package of a specific name in its repos) while the ccr equivalent is just cmd ccr -S "$@".

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?

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

No branches or pull requests

4 participants