This is an alternative package for Debian & Ubuntu systems. It is used for the "MythTV Light" packages for Raspberry Pi.
MythTV Light creates one package for MythTV and one package for the plugins, rather than multiple packages as generated by the main package setup. If you are building MythTV for your own backends and frontends you can copy a single file to each frontend and backend machine and install it.
MythTV Light creates a package of only the MythTV software. It does not install a database or setup any services, automatic backups, etc.
MythTV Light includes a suite of tools to support building and testing of multiple versions of MythTV on one computer. You can also test the built software before creating a package.
Set up your system this way.
- Clone the github MythTV/mythtv repository into a directory of your choice. The packages will be placed in the directory above the clone. For example if you clone into $HOME/project, git will create $HOME/project/mythtv and the packages will be placed in $HOME/project. Other files and directories will also be created in $HOME/project.
- Place the contents of github MythTV/packaging/deb-light repository into any directory.
- You can put the deb-light directory on your path to avoid entering it every time.
- Make sure you have the build dependencies installed. You can use the ansible repository to install them. See github MythTV/ansible.
If you want to override configuration options, you can either supply them on the command line of config.sh or add a MYTHTV_CONFIG_OPT_EXTRA line to $HOME/.buildrc, for example:
MYTHTV_CONFIG_OPT_EXTRA="--enable-opengl-video --enable-opengl"
Follow these steps to build the packages.
To build the mythtv-light package, run the following. <dir1> is the place you cloned the mythtv repository and <dir2> is the place the contents of packaging/deb-light are located:
cd <dir1>/mythtv/mythtv /<dir2>/build_package.sh
The first time you run this it will prompt for a build destination, defaulting to $HOME/proj/build.
Once the build is complete, the package will be in <dir1>. Also build logs and a directory containing the package data will be there. This directory is needed for the plugins build.
First build the mythtv-light package as described above.
Run the same way:
cd <dir1>/mythtv/mythplugins /<dir2>/build_package.sh
The package will be in <dir1>
The build_package.sh script runs 4 scripts. If you are developing or testing you can run them individually. This allows testing of multiple versions of MythTV on one system at the same time.
This script works from the mythtv or the mythplugins directory. It first cleans all old build data. It does not interfere with any source code changes or patches you may have made. It then runs configure with the normal options.
Before running config on mythplugins make sure you have already run config build and install on mythtv because the plugins need that.
config on mythplugins clears out mythtv build data as well as mythplugins build data. It also makes a copy of the mythtv install to run the build against.
After running config.sh, build.sh performs the make against the source.
This script installs the build into the directory selected for test builds the first time you run. It creates a hierarchy of directories for each environment and branch, so that you can have several branches and environments installed at once. It creates a separate directory for patched versions from github clean versions so that you can test a before and after scenario.
For mythtv it creates a directory called mythtv with subdirectories for each branch. For plugins it creates a directory called mythplugins with subdirectories. The mythplugins subdirectories contain both the mythtv and the plugins so that you can test mythtv with the plugins.
Versions that have git differences (dirty), are put in a directory with "-tst" appended tio the name. If you want a different extension applied, for example if you are working on multiple builds, add a "BUILD_DIRTY" line to $HOME/.buildrc, for example:
BUILD_DIRTY=ogl
This script creates a package from the installed build. It will check that the source version matches the built version.
This script uses up a mini environment in which you can test each version you have built:
test.sh <shortname> command
For example:
test.sh mdm mythbackend test.sh mdmt gdb mythfrontend
The shortname comes from file $HOME/.buildnames. Open that file and you will see lines like this:
shortname=xa4mtvmr longname=xenial-amd64/mythtv/master
You can edit the file and change them to something easier to remember. For example I use mdm for Mythtv Development Master. So edit the file and change it to something like this:
shortname=mdm longname=xenial-amd64/mythtv/master
Then you have to set up a .mythtv directory for each test version. It is named as $HOME/.mythtv-<shortname>, for example $HOME/.mythtv-mdm. This will contain details of your test database for that version.
Patched versions have "-tst" in their directory name and I add a t to the shortname:
shortname=mdmt longname=xenial-amd64/mythtv/master-tst
If you use the same .mythtv directory for .mythtv-mdm and .mythtv-mdmt you can create the one as a link to the other:
ln -s $HOME/.mythtv-mdm $HOME/.mythtv-mdmt
You can create multiple short names for the same version to test different scenarios:
shortname=mdmt longname=xenial-amd64/mythtv/master-tst shortname=mdmt1 longname=xenial-amd64/mythtv/master-tst
Then create $HOME/.mythtv-mdmt1 directory as a copy of $HOME/.mythtv-mdmt. Edit $HOME/.mythtv-mdmt1/config.xml and insert a LocalHostName that is different from your system id:
<LocalHostName>test1</LocalHostName>
By running as follows you can have two setups, such as different themes, screen settings or playback profiles:
test.sh mdmt mythfrontend test.sh mdmt1 mythfrontend