Required by (0)

Sources (3)

Enverex commented on 2016-08-16 15:03

As there is no lib32-twolame, can you add --disable-twolame to the configure stage? That way it'll stop people running into the issue they're currently seeing due to it seeing the 64bit lib and trying to link to that.

Roken commented on 2015-12-14 21:01

Well, it's not the end of the world. Packer to get the builds, then a manual pacman -U to install works. I'm sure it will work with other AUR helpers.

GordonGR commented on 2015-12-14 14:51

FadeMind: Thank you.

Rroken: Ah, now I understand. Yaourt does (or did, when I last used it) something similar: It would note that two packages must be updated. It would build one (so the other as well), install them both; then, for the second package, do the same thing all over again. These are bugs in the AUR helpers, I'm afraid. There is nothing to be done on our end and, of course, they are no reason to stop providing split packages. Lately I have been using cower. It only checks what packages need updating and downloads the source code for them (with -uud). Then it lets me compile them and build them myself.

FadeMind commented on 2015-12-14 12:14

--disable-twolame works here too.

Regards

Roken commented on 2015-12-13 15:30

Using an AUR helper (packer in my case) gives a "duplicate target" error of the build when it tries to install. I'm pretty sure that this is an error that is coming from pacman, though I'm less sure whether it's directly related to the two packages being built, or both packages being built in conjunction with a separate plugins package being available, effectively duplicating the plugins. Unfortunately, I don't know enough about how pacman works behind the scenes to speculate.

GordonGR commented on 2015-12-13 11:34

Roken, thanks for reply, I will add it to the PKGBUILD. I'm sorry though, I don't understand what you mean by "duplicate target". The idea behind split packages is that the code is compiled once and produces two packages at the same time. Then you can install one or both (but obviously foo-plugins depends on foo). [extra] does it the same way, yes, and I think it's reasonable. How would you prefer it?

Roken commented on 2015-12-13 08:29

--disable-twolame works here.

There is another issue which seems to be a result of the split package, and that is that lib32-gstreamer0.10-ugly also builds lib32-gstreamer-ugly-plugins, resulting in a "duplicate target" error. going to the build directory and installing each package manually works, and satisfies the update check, but surely if you are splitting the packages they should either be built exclusively by the package, or not be offered separately? (the same applies with gst bad packages)

GordonGR commented on 2015-12-12 14:57

FadeMind, nothing of the sort happens here. My guess is you have community/twolame installed, for which there is no lib32 counterpart, and that confuses the configure script. What happens if you try a --disable-twolame or something similar?