Bug 2308944 - [RFE:EPEL10] Please branch and build hdhomerun for EPEL10
Summary: [RFE:EPEL10] Please branch and build hdhomerun for EPEL10
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: hdhomerun
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andrew Bauer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2308762
Blocks: EPEL10Tracker
TreeView+ depends on / blocked
 
Reported: 2024-09-01 20:47 UTC by Gary Buhrmaster
Modified: 2024-09-25 13:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-09-25 13:40:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Proposed spec file patch (3.04 KB, patch)
2024-09-02 23:52 UTC, Gary Buhrmaster
no flags Details | Diff

Description Gary Buhrmaster 2024-09-01 20:47:20 UTC
Please branch and build hdhomerun for EPEL10

Note that EL10 does not include the GTK2 libraries that the current GUI application depends on, however, even if the libraries are made available, upstream has explicitly stated they have discontinued support for the GTK based GUI.

Comment 1 Xavier Bachelot 2024-09-02 13:12:22 UTC
I've built libicns, it should be available in the buildroot in 2 days or so.
Not sure what to do about the missing gtk2-devel. Guidance or even PR welcome, I unfortunately don't have time to look at that right now.

Comment 2 Andrew Bauer 2024-09-02 14:40:47 UTC
I wonder if this as simple as calling make hdhomerun_config, rather than make all:
https://github.com/Silicondust/libhdhomerun/blob/master/Makefile#L74

I can look at this after I return from vacation, along with the other packages the both of you have requested I build for epel10.

Comment 3 Gary Buhrmaster 2024-09-02 17:11:32 UTC
(In reply to Xavier Bachelot from comment #1)
> I've built libicns, it should be available in the buildroot in 2 days or so.
> Not sure what to do about the missing gtk2-devel. Guidance or even PR
> welcome, I unfortunately don't have time to look at that right now.

My suggestion would be to drop the GUI entirely.  Upstream has dropped support, and it does not have support for the latest features such as PLP support for ATSC 3.0 tuners (which makes it less useful going forward).  While not a GUI (and probably someone will complain), the hdhomerun_config cli program can provide all the information.  At the very least, until, unless GTK2 is made available in EPEL10, a few appropriate %if's and/or %bconds might work to not build the GUI for now.  I can try to work up a proposed patch if you agree on a path forward.

Note I am not in any hurry here, I am just starting the (long) process of finding various packages that are dependencies of my programs/packages (and I know that some of my requests end up having yet another long chain of dependencies, and so on, and so on).  My timeline is more towards release of RHEL10 proper, so 2025Q2 (although by release of C10S would be stretch goal).

Comment 4 Gary Buhrmaster 2024-09-02 23:52:56 UTC
Created attachment 2045236 [details]
Proposed spec file patch

*Proposed* spec file patch.

Very lightly tested.

A couple of notes:
- This adds a --with/--without gui option to the build, and defaults to on for existing releases, and off for EPEL10.
- If/when gtk2 be built for EPEL10, changing the conditional should be straighforward.
- A BR location was adjusted to simplify some of the ifdef'ry
- This preserves the "one spec file for all releases" goal (well, it is one of my goals).
- The Requires on gtk2 was removed since the rpm dependency generators pull in the needed libraries.

Comment 5 Andrew Bauer 2024-09-05 19:55:14 UTC
Thanks for the patch. That was close to what I had in mind.

https://koji.fedoraproject.org/koji/taskinfo?taskID=122998196

Comment 6 Andrew Bauer 2024-09-22 18:31:45 UTC
Re-opening this as the fedora packager has built gtk2 for el10:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-88b3bf3dce

Putting this here so I don't forget to look into this.


Note You need to log in before you can comment on or make changes to this bug.