Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#16372 - [mythtv] Split frontend/backend
Attached to Project:
Arch Linux
Opened by archist (archist) - Sunday, 27 September 2009, 14:45 GMT
Last edited by Giovanni Scafora (giovanni) - Saturday, 06 February 2010, 11:58 GMT
Opened by archist (archist) - Sunday, 27 September 2009, 14:45 GMT
Last edited by Giovanni Scafora (giovanni) - Saturday, 06 February 2010, 11:58 GMT
|
DetailsDescription:
At the upcomming release 0.22, it would be nice to split Mythtv into Mythbackend and Mythfrontend. Advantages are: * no need to install the mysql server, mythbackend, mythtv-setup on mythfrontends * no need to install mythfrontend files on the backend |
This task depends upon
Closed by Giovanni Scafora (giovanni)
Saturday, 06 February 2010, 11:58 GMT
Reason for closing: Won't implement
Saturday, 06 February 2010, 11:58 GMT
Reason for closing: Won't implement
Are you going to release a "release candidate" in the testing repository?
I cannot participate on Bug Squashing Day. But will do a 0.22 release tomorrow and hope to get rid of most bugs.
We could get rid of unnecessary dependency (if only frontend is used) using optdepends:
This will keep updating/maintaining much simpler: Any options?
The modified PKGBUILD splits the package into mythtv-common, mythtv-backend and mythtv-frontend. The first was necessary for libraries and programs both the frontend and backend use.
I have quickly tested the separate packages in virtualbox and they seem to work fine.
I have also added libavc1394 and libiec61883 as dependencies, because they are needed to make the --enable-firewire do something. I'm not sure whether I should open another ticker for this or just leave it here.
The last thing I added is an image and a desktop file to mythtv-frontend, so that you have a nice menu item for it. I kind of stole it from a mandriva srpm, but because I recognised the icon from the old GANT theme, this shouldn't be a problem.
I hope this will help you out
If it's not supported upstream, which it seems like it isn't, then I'm definitely against splitting the package.
I don't like the idea of potentially introducing extra bugs by moving away from upstream. This is also not in line with "The Arch Way" ("without unnecessary additions, modifications, or complications"[1] ).
Looking at the current mythtv-0.22-3 package it's only ~25MB download and ~52MB installed...I wouldn't break the upstream compatibility to save perhaps 25MB.
One vote from me on the optdepends to get rid of unnecessary dependencies.
[1] http://wiki.archlinux.org/index.php/The_Arch_Way