Bug 264431

Summary:	multimedia/libcec: RPI options creates conflict between misc/raspberrypi-userland and multimedia/kodi
Product:	Ports & Packages	Reporter:	Robert Clausecker <fuz>
Component:	Individual Port(s)	Assignee:	Po-Chuan Hsieh <sunpoet>
Status:	Closed FIXED
Severity:	Affects Some People	CC:	decke
Priority:	---	Keywords:	needs-qa
Version:	Latest	Flags:	bugzilla: maintainer-feedback? (sunpoet)
Hardware:	Any
OS:	Any
See Also:	https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225053
Bug Depends on:	225053
Bug Blocks:

Description Robert Clausecker freebsd_committer

2022-06-03 09:42:51 UTC

The port multimedia/libcec has an RPI option that pulls a dependency on misc/raspberrypi-userland.  Unfortunately that dependency later causes a
dependency conflict when multimedia/kodi is built as kodi also depends
on graphics/libglvnd (see bug #225053).

To make an armv7 build of multimedia/kodi at all possible, I propose to
make the RPI option no longer a default option, removing the dependency
on misc/raspberrypi-userland and hence resolving the dependency conflict.

Comment 1 Po-Chuan Hsieh freebsd_committer

2022-06-04 00:33:17 UTC

(In reply to Robert Clausecker from comment #0)

As you just pointed out, the key problem is the conflicts between misc/raspberrypi-userland and graphics/libglvnd.
I think it's better to fix this issue in bug #225053 if the patch there work for you.

Comment 2 Robert Clausecker freebsd_committer

2022-06-04 01:35:34 UTC

(In reply to Po-Chuan Hsieh from comment #1)

I will try to improve the patch from the other bug so it can be committed.  Right now my main concern is that this issue prevents the generation of binary packages for multimedia/kodi, which is one of the "killer applications" for armv7 devices.  So that's really not good.  Changing this one option to be non-default would fix the build of kodi for everybody who does not use a Raspberry Pi while probably being mostly harmless for Raspberry Pi users.

Comment 3 Robert Clausecker freebsd_committer

2022-06-04 10:49:00 UTC

Attachment #234432 [details] to bug #225053 fixes this issue.

Comment 4 Po-Chuan Hsieh freebsd_committer

2022-06-16 14:12:16 UTC

Problem solved after bug #225053 being committed. Thanks!