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

ark alias conflicts with Ark, the KDE archiving tool #88

Closed
PierreRustOrange opened this issue Apr 8, 2020 · 7 comments
Closed

ark alias conflicts with Ark, the KDE archiving tool #88

PierreRustOrange opened this issue Apr 8, 2020 · 7 comments

Comments

@PierreRustOrange
Copy link
Contributor

Expected Behaviour

When arkade is installed, my os basic tools should keep working... ;)

Current Behaviour

When arkade is installed, it creates a symlink /usr/local/bin/ark that override the ark utility ( located in /usr/bin/ark) which is used to handle all archive file on KDE desktops (tar, bz, etc.). All gui-based operations on these files are then broken (from the file manager, etc.).

Possible Solution

Avoid creating that alias by default, use a command line argument to create it only when explicitly requested.

@alexellis
Copy link
Owner

Hi @PierreRustOrange would it be useful to you if we have an env-var to suppress the alias?

export CREATE_ARKADE_ALIAS=0

@PierreRustOrange
Copy link
Contributor Author

Thanks for your answer.

I'd rather have an env-var to create the alias than to suppress it, it's actually very easy to fix the problem (only need to rm the symlink), the only difficult part is to identify it. It took me some time to understand why I could not open any tar.gz anymore...
Either way, as long as it is mentioned in the doc I'd say it's fine !

@alexellis
Copy link
Owner

What if we checked for ark existing in PATH before creating it? Would that resolve this issue?

@PierreRustOrange
Copy link
Contributor Author

That's a great idea, that would completely resolve the issue and could probably be implemented by simply checking the return form whereis ark before creating the symlink.

@alexellis
Copy link
Owner

I know you didn't come here necessary to write a PR, but would you be up for giving it a shot? we use get.sh in this repo.

@PierreRustOrange
Copy link
Contributor Author

You're right, I should have done that before.
The PR is done, my bash is probably a bit rusty, there might be a more efficient way to implement that check but it seems to do the trick.

@Waterdrips
Copy link
Contributor

/close
This was implemented in #89
thanks

@derek derek bot closed this as completed Oct 31, 2020
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

No branches or pull requests

3 participants