Please readd this ebuild that was removed as part of bug 665924. mythplugins was not made obsolete by mythtv-29 and still very much exists and is being maintained (as of 3 days ago). It can be found here: https://github.com/MythTV/mythtv/tree/master/mythplugins
Created attachment 565806 [details] Draft ebuild to solve this bug This is based on the -0.28 ebuild. I pulled the mythtv dependency because I wasn't getting it right. I didn't check any dependencies that may have been added, removed, or updated. It works for me.
While the ebuild I attached works just fine, the best solution would be to update the mythtv ebuild to recognize the flags for the various plugins and build them as part of the same build. For now, though, this is a quick fix to let everyone get up to 29.1 while we wait for a -30 ebuild.
Created attachment 566834 [details] mythtv-29.1-r2.ebuild My previous attachment was an ebuild to restore the mythplugins, but now I offer a modification of the media-tv/mythtv ebuild that includes both the base myth and the plugins. With the separate ebuild, I had problems upgrading an existing system, and you're really stuck if you upgrade one and find the other breaks. Having both together really is the right solution. The ebuild I'm uploading is a bit of a hack merging the two. I'm not an ebuild expert, but it works. It's a bit of a hack, so maybe someone else can clean it up. It has to configure, compile, and install in two different subdirectories, making it a bit complicated. Also, the dependencies for the plugins are probably too much, but it's a straight copy of the mythplugins ebuild dependencies with everything copied for each plugin, though I suspect many didn't need everything. I don't have a minimalist system where I can remove all the dependencies, see what fails, and add them back in only as needed. I also can't find solid documentation from the MythTV side on what the dependencies are supposed to be.
MythTV is a complicated build, and there are problems with both the separate mythplugins ebuild and the combined one. With the separate ebuild, you can't cleanly upgrade an existing system. If you tell it to build both, it will start both, doing the mythplugins first, and it will fail. If the jobs run in parallel, the mythtv build will succeed, and then you can do the mythplugins again, and it will succeed, but you can't just do mythtv first, as it's blocked by the older mythplugins already installed. With the new combined ebuild, it works fine if you already have mythtv installed, but if it's a new install, you have to install it without any plugins first, then install again with the plugins. The building of the plugins looks for some files that are part of the mythtv install, and I haven't figured out yet how to do it all right in one ebuild. I think what is needed is to have the ebuild configure, compile, and install mythtv first, then do the same for mythplugins. I'm not an ebuild expert, so I'm not clear on how to do this. It also feels counter to the general design of the ebuild system. While I was digging into this, I thought about having flags for only building the frontend or backend (I want to run a separate backend and several frontends). The configure script has this disabled due to "abuse in Gentoo ebuild." Apparently the MythTV people didn't like how this was used back in 2007 or so; I think they were separate ebuilds instead of one with configuration options, but I don't remember for sure.
Created attachment 567742 [details] mythtv-29.1-r2.ebuild It took a lot of work, but I now have an ebuild that includes the plugins in media-tv/mythtv. From a user perspective, this is the right way to do it. If you are upgrading a system, you don't want to proceed unless you have everything ready. The worst option would be to have the base upgrade only to find that the plugins aren't working. From a developer perspective, this is a big ugly hack. While the plugins and the base are part of the same source distribution, they are built separately. The plugins build using both include files and library files that are installed from the base. It takes a good bit of hacking to make this work in the ebuild. This ebuild has several things I generally don't see in other ebuilds. Most notably, I've included lots of comments to explain all the things it's doing. The worst part is doing the install of the base in the compile phase so that the plugins can find everything in the image directory to build from, and then it's installed again in the install phase because the image directory is wiped. I wasn't able to find a way to tell the ebuild that it replaces both media-tv/mythtv and media-plugins/mythplugins to make upgrading seamless. If there's a feature in portage to allow an ebuild to replace two ebuilds, please explain here or update the ebuild to do so.
Created attachment 568334 [details] mythtv-30.0.ebuild I updated the 29 ebuild I posted previously for version 30 based on changes in bug 676952. This incorporates the work in the ebuild posted in that bug, and it requires the patch file 'mythtv-30.0-configure-NVCtrl.patch' posted with that bug. I spent a lot of time looking at the configuration options in the MythTV configure script, so I updated the use flags to match. I added some new use flags for video capture devices. I left off a couple of devices that don't have required dependencies in portage (crystalhd and dveo). There are still some configuration options that don't have use flags. I ordered the ebuild setting of configuration options to match the order that the MythTV configure script reports options, leaving comments where options aren't configured. Frankly, the items left in the MythTV configuration that aren't set one way or the other by use flags are things I don't really understand, so I left them to default as they always have been. New in 30 is the Blu Ray support, which is required, but the Java support for menus is optional (and now controlled with the 'java' use flag). This still has the 'altivec' use flag that only applies to PPC builds. Unless someone is going to test this on PPC, we should probably pull that. The new use flags will require a metadata.xml file to list them with descriptions if this is to be included in portage. I've spent a lot of time on this, so I would really like feedback on whether this is a good approach.
The new mythtv-30.0 ebuild built fine on my ryzen 2700 system. I tried to run the frontend but it wanted to upgrade my database so I had to exit. I am still using 29.1 on my master backend. I will upgrade that soon and test. To me the combined ebuild makes some sense since you always build both plugins and mythtv each time you upgrade.
*** Bug 676952 has been marked as a duplicate of this bug. ***
Created attachment 573220 [details, diff] Patch to configure NVCtrl to us external xnvctrl when nvidia-drivers[tools] installed Select internal or external xnvctrl.
Thanks for referencing this in the other bug. I think that configure patch will generate a bash missing ] error(?). I was actually going to just base mine on the existence of /usr/bin/nvidia-settings. I'll attach what I was going to use. For myself, especially since I don't use any of the plugins and am also using changes to allow me to omit the dependencies on udisks, qtdbus, and qtwebkit, I'll probably end up using a modified version more like the 29.1 ebuild for simplicity's sake. Looks like that plugin addition wasn't trivial. I'll probably attach that in case anyone's interested. I was also curious: Is the >=media-libs/libbluray-0.9.3 actually needed when the bluray USE isn't set? Thanks for all the effort!
Created attachment 573364 [details, diff] Alternate patch to use internal NVCtrl when nvidia-drivers[tools] not installed.
In answer to my own question, I see that the --enable-libbluray configure option is gone, so apparently it's required now.
I compiled mythtv-30.0.ebuild on my system. It requires 72 new dev-java/... packages that were not already installed on my system. I narrowed it down to a line in COMMON=" ... java? ( dev-java/ant ) ... " On my system "java" use flag is globally enabled. I removed the line from my copy of ebuild and it no longer needs to build 72 more dev-java/... packages. According the the Ant website: "The main known usage of Ant is the build of Java applications." To be sure it was not required to compile and install any plug ins, I added use flags: "mytharchive mythbrowser mythgallery mythgame mythmusic mythnetvision mythweather mythzoneminder" This compiled correctly and installed. I appears that java is only used with bluray (which is also globally enabled on my system). If some of the plug ins use dev-java/ant. java? ( dev-java/ant ) needs to be moved to the plug ins that require it. What did I miss?
--enable-libbluray can be found in the file mythtv/external/FFmpeg/configure: --enable-libbluray enable BluRay reading using libbluray [no]
One other suggestion here that I ran into when comparing my existing ebuild: While the attached ebuilds here don't have the virtual/mysql dependency they had at one time (which is correct, as that functionality is going away), it might be a good idea to have the logic in pkg_config() conditional on the existence of the mysql client program. See my notes the ebuild I attached to bug 665928.
Is there no support for mythweb in the mythtv-30.0 ebuild?
Sorry user error. mythweb is a separate ebuild.
I am now using the mythtv-30.0 ebuild in production. So far so good.
I'm having problems getting the 30 ebuild to build and install the plugins. Does anyone have that feature of the ebuild working? I must be doing something wrong with the use flags, but haven't figured it out yet.
Created attachment 581452 [details] ebuild for mythtv 30 with working plugins I'm not sure this is the most efficient way to fix the ebuild, but it does work. The problem was the way the script was testing 'use ${MYTHPLUGINS}' which is never true. I added a function to check for any mythplugin use to set a variable and then use that variable to determine whether to configure, build and install mythplugins.
I am trying to update the ebuild to mythtv-30 as a first time proxy-maintainer. So far I edited the metadata.xml files for the use flags. I plan to make a pull request to update the gentoo tree. For years I have used mythtv without plugins. Upstream keeps mythtv and mythplugins in separate directories. The documentation requires that mythtv be installed before compiling mythplugins. It makes sense to have both media-tv/mythtv and media-plugins/mythtv-plugins as separate gentoo packages. Is there a reason they need to be combined into one package?
(In reply to Wilson M. Michaels from comment #21) [Edit] The plugins package should be media-plugins/mythplugins -- same as previous versions.
mythtv-30.0_p20190808 is now in gentoo! (without mythplugins) I am working on the media-plugins/mythplugins package. Mythtv is a big package. Select the plugins you don't want with USE flags to add/remove them without recompiling the whole media-tv/mythtv package for the same version.
mythtv-30.0_p20190808 does not build for me. Attaching log.
Created attachment 590634 [details] mythtv-30.0_p20190808 build error mythtv-30.0_p20190808 build error.
(In reply to thomas from comment #25) > Created attachment 590634 [details] > mythtv-30.0_p20190808 build error > > mythtv-30.0_p20190808 build error.
(In reply to Wilson M. Michaels from comment #26) > (In reply to thomas from comment #25) > > Created attachment 590634 [details] > > mythtv-30.0_p20190808 build error > > > > mythtv-30.0_p20190808 build error. XNVctrl is provided by propritary x11-drivers/nvidia-drivers It is not available with nouveau or intel drivers. I will add a dependency.
Hi, today I updated to mythtv-30.0_p20190808 on my headless backend and on my frontends. It worked out of the box here without any build errors on every machine. None of them has an NVidia-based graphics card. Thank you very much for keeping MythTV alive! My feedback for the current ebuild: great work :) Regards, Florian
(In reply to Wilson M. Michaels from comment #27) > XNVctrl is provided by propritary x11-drivers/nvidia-drivers > > It is not available with nouveau or intel drivers. > > I will add a dependency. I do have nvidia-drivers installed. Although I read somewhere else that they also need to have static-libs enabled? Can you add this also in the dependency? Thanks!
(In reply to thomas from comment #29) > (In reply to Wilson M. Michaels from comment #27) > > XNVctrl is provided by propritary x11-drivers/nvidia-drivers > > > > It is not available with nouveau or intel drivers. > > > > I will add a dependency. > > I do have nvidia-drivers installed. Although I read somewhere else that they > also need to have static-libs enabled? Can you add this also in the > dependency? Thanks! Did you build nvidia-drivers with the "tools" USE flag?
(In reply to Wilson M. Michaels from comment #30) > Did you build nvidia-drivers with the "tools" USE flag? Yes.
(In reply to thomas from comment #31) > (In reply to Wilson M. Michaels from comment #30) > > > Did you build nvidia-drivers with the "tools" USE flag? > > Yes. I added a dependency. I need clarification. Does building without static-libs work? sudo USE="tools -static-libs" emerge -v nvidia-drivers sudo emerge -v =media-tv/mythtv-30.0_p20190808 Is static-libs actually required?
(In reply to Wilson M. Michaels from comment #32) > Does building without static-libs work? > > sudo USE="tools -static-libs" emerge -v nvidia-drivers > sudo emerge -v =media-tv/mythtv-30.0_p20190808 > > Is static-libs actually required? I do have +tools and -static-libs and it does not build. Someone mentioned that nvidia-drivers only includes the necessary headers if you have +static-libs.
I am working on the original bug for mythplugins. Please create new bug for other topics. I am creating Bug #695684 so I can fix it and leave this bug open.
M(In reply to Preston Crow from comment #6) > Created attachment 568334 [details] > mythtv-30.0.ebuild > > I updated the 29 ebuild I posted previously for version 30 based on changes > in bug 676952. This incorporates the work in the ebuild posted in that bug, > and it requires the patch file 'mythtv-30.0-configure-NVCtrl.patch' posted > with that bug. > > I spent a lot of time looking at the configuration options in the MythTV > configure script, so I updated the use flags to match. I added some new use > flags for video capture devices. I left off a couple of devices that don't > have required dependencies in portage (crystalhd and dveo). There are still > some configuration options that don't have use flags. I ordered the ebuild > setting of configuration options to match the order that the MythTV > configure script reports options, leaving comments where options aren't > configured. > > Frankly, the items left in the MythTV configuration that aren't set one way > or the other by use flags are things I don't really understand, so I left > them to default as they always have been. > > New in 30 is the Blu Ray support, which is required, but the Java support > for menus is optional (and now controlled with the 'java' use flag). > > This still has the 'altivec' use flag that only applies to PPC builds. > Unless someone is going to test this on PPC, we should probably pull that. > > The new use flags will require a metadata.xml file to list them with > descriptions if this is to be included in portage. > > I've spent a lot of time on this, so I would really like feedback on whether > this is a good approach. Thank you for reporting the results on your work. I am moving this discussion to Bug 695688 since it may not be found under mythplugins title.
Somehow the mythtv-29.1-r2 ebuild now appeared in portage. I won't upgrade to 30.0 yet because of still missing mythplugins 30.0. But the mythtv-29.1-r2 ebuild does not build: ERROR: media-tv/mythtv-29.1-r2::gentoo failed (prepare phase): * The source directory '/var/tmp/portage/media-tv/mythtv-29.1-r2/work/mythtv-29.1-r2/mythtv' doesn't exist And -r1 is gone. Anyone any idea?
(In reply to thomas from comment #36) > Somehow the mythtv-29.1-r2 ebuild now appeared in portage. I won't upgrade > to 30.0 yet because of still missing mythplugins 30.0. > > But the mythtv-29.1-r2 ebuild does not build: > ERROR: media-tv/mythtv-29.1-r2::gentoo failed (prepare phase): > * The source directory > '/var/tmp/portage/media-tv/mythtv-29.1-r2/work/mythtv-29.1-r2/mythtv' > doesn't exist > > And -r1 is gone. > > Anyone any idea? Yes, I noticed that as well. There appears to be a bug in the ebuild. It has an incorrect SRC_URI that has -r1 instead of -r2 in the target file name. I corrected that locally and it worked. I intended to report a bug but it slipped my mind :-( I'll attach a patch here.
Created attachment 592586 [details, diff] Patch to fix mythtv-29.1-r2.ebuild
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6b5e29fcd322f509e442e7b48812c51ca15835b7 commit 6b5e29fcd322f509e442e7b48812c51ca15835b7 Author: Wilson Michaels <thebitpit@earthlink.net> AuthorDate: 2019-10-12 18:05:36 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2019-10-12 21:22:03 +0000 media-tv/mythtv: bug fix mythtv-29.1-r2.ebuild source directory name Closes: https://bugs.gentoo.org/674216 Package-Manager: Portage-2.3.76, Repoman-2.3.16 Signed-off-by: Wilson Michaels <thebitpit@earthlink.net> Closes: https://github.com/gentoo/gentoo/pull/13269 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> media-tv/mythtv/mythtv-29.1-r2.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Why is there no mythplugins 30.0 in portage?
I accidentaly closed this bug. Trying to figure out why gentoo developers can not compile zmserver daemon. It builds on my system OK. Pull request for mythplugins is: https://github.com/thebitpit/gentoo/pull/new/media-plugins%2Fmythplugins Here's the problem: [ebuild R ] dev-db/mysql-connector-c-8.0.18:0/21::gentoo USE="ldap -libressl -static-libs" ABI_X86="32 (64) (-x32)" 0 KiB [ebuild N ] media-plugins/mythplugins-30.0::testworld USE="alsa cdda cdr exif hls mytharchive mythbrowser mythgallery mythgame mythmusic mythnetvision mythnews mythweather mythzmserver mythzoneminder opengl theora vorbis xml xvid -fftw -ieee1394 -libass -raw" PYTHON_TARGETS="python2_7" 0 KiB zmserver.cpp: In function ‘void connectToDatabase()’: zmserver.cpp:186:5: error: ‘my_bool’ was not declared in this scope; did you mean ‘bool’? 186 | my_bool reconnect = 1; | ^~~~~~~ | bool zmserver.cpp:187:52: error: ‘reconnect’ was not declared in this scope; did you mean ‘connect’? 187 | mysql_options(&g_dbConn, MYSQL_OPT_RECONNECT, &reconnect); | ^~~~~~~~~ | connect make[2]: *** [Makefile:406: obj/zmserver.o] Error 1 make[2]: *** Waiting for unfinished jobs.... I can not duplicate this on my system. my_bool is defined in header file in package dev-db/mysql-connector-c
(In reply to Wilson M. Michaels from comment #41) > I accidentaly closed this bug. > > Trying to figure out why gentoo developers can not compile zmserver daemon. > It builds on my system OK. Pull request for mythplugins is: > > https://github.com/thebitpit/gentoo/pull/new/media-plugins%2Fmythplugins > > > Here's the problem: > [...] > > I can not duplicate this on my system. my_bool is defined in header file in > package dev-db/mysql-connector-c my_bool is no longer in the include file mysql.h in =dev-db/mysql-connector-c-8.0.18 which is unstable in Gentoo. So I suspect the gentoo developers are using that version. The stable version 6.1.11-r2 /does/ define my_bool. You could change the ebuild to depend on <dev-db/mysql-connector-c-8.0.0 so it will only build with the stable version. Its also possible that the mythtv developers have a fix in a later version, so you could perhaps generate a patch from that and apply it to the mythtv version you are using.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=33381f89cf2a48894b5fddab827d66e95a165a7f commit 33381f89cf2a48894b5fddab827d66e95a165a7f Author: Wilson Michaels <thebitpit@earthlink.net> AuthorDate: 2019-09-21 16:53:40 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2019-11-18 06:14:14 +0000 media-plugins/mythplugins: new package - v. 30.0 Reviving package that previously was in gentoo with new version. Bug: https://bugs.gentoo.org/674216 Package-Manager: Portage-2.3.76, Repoman-2.3.16 Signed-off-by: Wilson Michaels <thebitpit@earthlink.net> Closes: https://github.com/gentoo/gentoo/pull/13109 Signed-off-by: Joonas Niilola <juippis@gentoo.org> media-plugins/mythplugins/Manifest | 1 + media-plugins/mythplugins/metadata.xml | 32 +++++ media-plugins/mythplugins/mythplugins-30.0.ebuild | 168 ++++++++++++++++++++++ 3 files changed, 201 insertions(+)
All PRs are closed. Anything left to do in this ticket? Should it be closed?
Please close this bug.
