Package Details: kodi-devel 18.4rc1pre23-1

Git Clone URL: (read-only)
Package Base: kodi-devel
Description: Alpha, Beta, or RC versions of the software media player and entertainment hub for digital media
Upstream URL:
Keywords: kodi kodi-devel
Licenses: GPL2
Conflicts: kodi
Provides: kodi=18.4rc1pre23
Submitter: alucryd
Maintainer: MarcinWieczorek (graysky)
Last Packager: graysky
Votes: 32
Popularity: 0.055671
First Submitted: 2014-08-11 23:33
Last Updated: 2019-08-17 18:16

Dependencies (63)

Required by (45)

Sources (33)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

asm0dey commented on 2019-08-17 12:22

That's bacause "$pkgbase-bin" is declared. Please change it to kodi-bin-devel. Thank you!

asm0dey commented on 2019-08-17 12:20

I've got following error when trying to clean install package:

warning: cannot resolve "kodi-devel-bin", a dependency of "kodi-devel"
:: The following package cannot be upgraded due to unresolvable dependencies:

asm0dey commented on 2019-08-14 07:01

Also potentially it makes sense to rename -bin to -x11 (because -wayland builds binary too)

graysky commented on 2019-08-13 19:19

I agree about the confusion around the -bin suffix for the package in community. Has anyone considered opening a FS to change it? I am fine changing the order of -component-devel to a system that makes sense to people/I don't have a strong opinion either way.

Am I correct that the proposal is:

  "kodi-bin-devel" "kodi-wayland-devel" "kodi-gbm-devel"
  "kodi-eventclients-devel" "kodi-tools-texturepacker-devel" "kodi-dev-devel"

eschwartz commented on 2019-08-12 22:42

That makes no sense, the official repos don't have devel packages to emulate. But look at git packages. For example, systemd-git and systemd-libs-git, not systemd-git-libs. The package could be seen as being "kodi-x11binarycomponent", so why would a person think to insert the "devel" in the middle of the community pkgname which it replaces.

It's probably more relevant that you have, for example, "kodi-devel-tools-texturepacker". Would someone looking for the development version of the texturepacker package be looking for such a package name?


The fact that this discussion centers around the "kodi-devel-bin" component is only because it was especially confusing due to the surprising presence of "-bin" at all. (I personally wonder why the community package is named that at all, instead of "kodi-x11".)

graysky commented on 2019-08-12 21:54

@asm0dey - Not sure what the convention is for a -devel package... made sense to me to append the -devel to the $pkgbase. Can you cite an example or two in the official repos one way or another?

asm0dey commented on 2019-08-12 19:44

So, little more thinks about package naming. Actually kodi-devel-bin is not binary package. Looks like it's -devel version of community package kodi-bin, so potentially better naming would be kodi-bin-devel (which won't broke -bin contract also).

Also name kodi-bin of original package is strange too: looks like it should be name kodi-x11.

Overall it looks to me and to Eli Schwartz (gratitude to him for the idea behind this comment) that naming is not completely consistent and we would prefer it to be changed.

asm0dey commented on 2019-08-09 08:31

I'm trying to install kodi-devel-bin, but it starts to compile and it takes like forever. Doesn't it break contract for -bin packages?

Kr1ss commented on 2019-07-28 20:50

Hi @graysky, thx for the update ! Although 009-PR16378.patch is failing here. I've uploaded a prepare() log to

Freso commented on 2019-04-29 18:40

My notion was mostly to, as graysky said, keep in sync with the kodi package from the official Arch repositories.