| View previous topic :: View next topic |
| Author |
Message |
fert
n00b
Joined: 19 Sep 2007
Posts: 40
|
 Posted: Sat Dec 03, 2016 11:33 pm Post subject: mythtv and chromium -- can libvpx be slotted? |
 |
|
OK, so it has been a while now that I've had to keep libvpx at 1.4.0 in order for mythtv to remain. This also means that chromium can't be built because it requires libvpx with svc flag which isn't available until libvpx-1.5.0.
It's obvious that I don't know the details of how slotting works, but why can't libvpx be slotted so that I could have 1.4.0 and >=1.5.0 on the same system? I would then be able to have chromium and mythtv working on the same system, no? |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54232
Location: 56N 3W
|
| Posted: Sat Dec 03, 2016 11:46 pm Post subject: |
|
|
fert,
Slotting would not solve your problem.
With slotting comes a way to make one version active.
Think gcc-config. gcc is slotted.
Slotting allows two versions to be installed at the some time, not work at the name time.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
fert
n00b
Joined: 19 Sep 2007
Posts: 40
|
| Posted: Sat Dec 03, 2016 11:51 pm Post subject: |
|
|
Oh. Then I completely misunderstood portage's slotting. I thought its purpose was to have more than one version of a library installed--exactly what would be needed, it seems, for mythtv and chromium to exist on the same system.
Bummer. |
|
| Back to top |
|
|
Jaglover
Watchman
Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana
|
|
| Back to top |
|
|
fert
n00b
Joined: 19 Sep 2007
Posts: 40
|
| Posted: Sun Dec 04, 2016 12:35 am Post subject: |
|
|
| Jaglover wrote: | | You can unmask 0.28 if you are willing to test it. |
But 0.28 requires libvpx <1.5.0 as well.
Looks like the only way to have chromium and mythtv is to disable live streaming (-hls) in mythtv.
Maybe it is possible to just disable the libvpx support, and rely solely on h264 for the video--tbd. |
|
| Back to top |
|
|
danomac
l33t
Joined: 06 Nov 2004
Posts: 881
Location: Vancouver, BC
|
| Posted: Mon Dec 05, 2016 7:29 pm Post subject: |
|
|
| I ran into this recently, but I don't use chromium. ffmpeg wanted the newer version, but would build with the old version, so I masked it for now. Mine are dedicated mythtv frontends however. |
|
| Back to top |
|
|
WillemM
n00b
Joined: 01 Dec 2007
Posts: 11
|
| Posted: Tue Dec 06, 2016 10:24 am Post subject: |
|
|
Thanks, this work around works for me. I would like to make some time for testing 0.28, it is out since April I see.
| fert wrote: | | Jaglover wrote: | | You can unmask 0.28 if you are willing to test it. |
But 0.28 requires libvpx <1.5.0 as well.
Looks like the only way to have chromium and mythtv is to disable live streaming (-hls) in mythtv.
Maybe it is possible to just disable the libvpx support, and rely solely on h264 for the video--tbd. |
|
|
| Back to top |
|
|
skwang
Tux's lil' helper
Joined: 12 May 2004
Posts: 149
Location: Chicago, IL
|
| Posted: Tue Dec 13, 2016 11:33 pm Post subject: |
|
|
I compiled the mythtv-0.28 ebuilds with libvpx 1.5.
1) I copied the mythtv directory from /usr/portage/media-tv to /usr/local/portage/media-tv.
2) Then I deleted all but the v0.28 ebuild, as well as the Manifest and the metadata.xml files.
3) I edited the ebuild to flip the sign of libvpx.
| Code: | --- /usr/portage/media-tv/mythtv/mythtv-0.28.ebuild 2016-10-02 07:36:50.000000000 -0500
+++ /usr/local/portage/media-tv/mythtv/mythtv-0.28.ebuild 2016-12-12 14:11:10.917097625 -0600
@@ -72,7 +72,7 @@
fftw? ( sci-libs/fftw:3.0= )
hls? (
media-libs/faac:=
- <media-libs/libvpx-1.5.0:=
+ >=media-libs/libvpx-1.5.0:=
>=media-libs/x264-0.0.20111220:=
)
ieee1394? (
|
Then I ran | Code: | ebuild mythtv-0.28.ebuild digest
emerge mythtv |
I ran into one speedbump: http://lists.mythtv.org/pipermail/mythtv-users/2016-May/387001.html. I had to manually install media-gfx/exiv2 and dev-qt/qtxml before mythtv would compile properly. The 0.28 ebuild does not list them dependencies, when they probably should be included.
Mythtv 0.28 seems to work. And now I can emerge chromium (in theory). (Update: I'm having chromium build errors but I believe it is unrelated to the libvpx issue discussed in this thread.) |
|
| Back to top |
|
|
|
Portage & Programming
