[SOLVED] app demands other package-name. create a link?

Asbestbrezel · 2019-01-07 11:25:20

Hello,

im currently using asunder to digitalize my cd-collection. I want to use opus-codec. If i go to activate opus in the asunder-options it demands 'opusenc' as a package. But in arch repos its named just 'opus'. So for now it does not work.
Can i create a kind of link of the opusenc to opus. Or what would be the best method to deal with this problem?

Last edited by Asbestbrezel (2019-01-07 12:14:51)

schard · 2019-01-07 11:47:49

Asbestbrezel wrote:

Or what would be the best method to deal with this problem?

The optimal solution would be to open a feature request on the bug tracker regarding the package "opus" asking the maintainer to add "opusenc" to the provides array.
The quickest solution is to create an empty package on your own named "opusenc" having "opus" as sole dependency.
Edit: Fixed Arch package name.

Last edited by schard (2019-01-07 12:04:49)

Lone_Wolf · 2019-01-07 11:53:01

Don't link.

run pacman -Ss opus .
Do you see something that might solve the issue ?

Asbestbrezel · 2019-01-07 12:14:21

ok, thank you, lone-wolf. opus-tools did the job.

@schard: good idea though, will maybe become useful in the future, i guess

progandy · 2019-01-07 12:17:27

If you want to know which package provides a binary, then you can use the -F commands.

$ sudo pacman -Fy
$ pacman -Fs opusenc
community/opus-tools 0.2-1
    usr/bin/opusenc

Edit: Asunder should probably have opus-tools as an optional dependency, though.

Last edited by progandy (2019-01-07 12:21:08)

schard · 2019-01-07 12:20:36

Yeah. OP spoke of a demanded *package* 'opusenc', so I assumed asunder was checking the package DB, not for a specific binary.
If I'd have had this information beforehand, I would not have suggested modifying or creating a package.

progandy · 2019-01-07 12:25:13

@schard: If an application demands a "package" in a dialog or error message and you can't find it, then search for it as a binary name as well. Normally applications don't know anything about the package manager and installed packages, but they do know about files like libraries and binaries.

Asbestbrezel · 2019-01-07 12:59:23

okay. so that was my idea at first. create a link to the binary 'opus'. would that work if it would be the case?

schard · 2019-01-07 13:14:15

Maybe. But links will pollute your system and may cause unwanted side-effects on later updates or new software. So, as Lone_Wolf already pointed out, don't do that.

Asbestbrezel · 2019-01-07 14:09:39

yes, but it could become handy as a quick'n'dirty solution, until the developer fixed it.

Trilby · 2019-01-07 14:35:13

Asbestbrezel wrote:

okay. so that was my idea at first. create a link to the binary 'opus'. would that work if it would be the case?

If what would be the case?

I highly doubt those binaries are the same (edit: see below, they are not as only one of them actually exists). If on the off chance they actually are identical, that would be a harmless but sub-optimal solution.

As for your last post, there is nothing for the developers to fix. One program you ran asked you to ensure you had another program installed. Check the repos for that program and install it.

EDIT: *headdesk*, the package `opus` does not contain anything under /usr/bin and nothing named 'opus' - so what exactly would you link to?

Last edited by Trilby (2019-01-07 14:37:54)

Asbestbrezel · 2019-01-07 16:31:39

i remember that parrot. always nose up.

i assumed 'opus' is the right package, because it says so on the german asunder wiki site.
https://wiki.archlinux.de/title/Asunder
Also in the english wiki about codecs, just this 'opus' is mentioned.
https://wiki.archlinux.org/index.php/Codecs

With that case, i mean a possible problem of that kind, that i could run into in the future.
So maybe a program (that, i want to install in the future) demands a package, that is named different, than the one in the arch-repos. I can use this quick and dirty solution until the dev (of that programm, that i MAYBE want to install in the FUTURE) fixed that problem, after i contacted him.

I hope i explained well enough for you, inspector.

Trilby · 2019-01-07 16:36:13

No, your quick and dirty solution would not work. Again, what exactly would it be? What is the symlink command you were thinking of using? The binary opusenc is not equivalent to anything in the opus package, there is nothing within the opus package to which you could create a symlink named opusenc.

As for the "nose up" comment, I don't recall any previous interactions with you, but I will make your day and ensure I never try to help you again in the future.

Last edited by Trilby (2019-01-07 16:37:51)

Asbestbrezel · 2019-01-07 16:38:06

I'm not talking about that opus thing any more. I'm talking about any kind of program, that maybe has a binary missing.

Arch Linux

#1 2019-01-07 11:25:20

[SOLVED] app demands other package-name. create a link?

#2 2019-01-07 11:47:49

Re: [SOLVED] app demands other package-name. create a link?

#3 2019-01-07 11:53:01

Re: [SOLVED] app demands other package-name. create a link?

#4 2019-01-07 12:14:21

Re: [SOLVED] app demands other package-name. create a link?

#5 2019-01-07 12:17:27

Re: [SOLVED] app demands other package-name. create a link?

#6 2019-01-07 12:20:36

Re: [SOLVED] app demands other package-name. create a link?

#7 2019-01-07 12:25:13

Re: [SOLVED] app demands other package-name. create a link?

#8 2019-01-07 12:59:23

Re: [SOLVED] app demands other package-name. create a link?

#9 2019-01-07 13:14:15

Re: [SOLVED] app demands other package-name. create a link?

#10 2019-01-07 14:09:39

Re: [SOLVED] app demands other package-name. create a link?

#11 2019-01-07 14:35:13

Re: [SOLVED] app demands other package-name. create a link?

#12 2019-01-07 16:31:39

Re: [SOLVED] app demands other package-name. create a link?

#13 2019-01-07 16:36:13

Re: [SOLVED] app demands other package-name. create a link?

#14 2019-01-07 16:38:06

Re: [SOLVED] app demands other package-name. create a link?

Board footer