Installscript: Difference between revisions

From VDR Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 26: Line 26:
* config/[[INSTALLSCRIPT kernel.conf|'''kernel.conf''']]
* config/[[INSTALLSCRIPT kernel.conf|'''kernel.conf''']]
* config/[[INSTALLSCRIPT configure.conf|'''configure.conf''']]
* config/[[INSTALLSCRIPT configure.conf|'''configure.conf''']]
* config/[[installscript-marks2pts.conf|'''marks2pts.conf''']]
* examples/plugins/[[INSTALLSCRIPT accounts.conf|'''accounts.conf''']]
* examples/plugins/[[INSTALLSCRIPT accounts.conf|'''accounts.conf''']]
e.g. with the ''mcedit'' editor
e.g. with the ''mcedit'' editor
mcedit config/setup.conf
mcedit config/setup.conf

In '''../config/plugins''' befinden sich die Einstellungen der Plugins, als bsp das [[audiocd-plugin]]. '''../config/plugins/audiocd.conf'''
## Description:
#
# -d DEV --device=DEV set device (default: /dev/cdrom)
#
##
-d /dev/cdrom

Options are prefaced with '''<code>^-</code>''', after selection it goes into the '''plugin_setup.conf''', see [[pluginsetup-plugin]], the same for '''Description'''.
## Description: AudioCD Plugin
^^^^^^^^^^^^^^
Würde später im Menu des Plugins (pluginsetup) stehen, ansonnsten <NAME>


Most of the options can be delivered through the commandline, independently from '''setup.conf'''
Most of the options can be delivered through the commandline, independently from '''setup.conf'''
Line 54: Line 68:
./setup.sh --buildrunpackage
./setup.sh --buildrunpackage
Label (default "vdr-install-script-<VERSION>.run"):
Label (default "vdr-install-script-<VERSION>.run"):

Gesichert wird, was in '''../setup/SAFE''' definiert wurde.

#
# FILE(s) only txt files!
#
../setup/config/add.conf
#
# DIRECTORY(ies) maxdepth 1, only txt files!
#
../setup/config/plugins

Wer möchte kann auch Files "außerhalb" der Scripts sichern, einfach eintragen.
#
# FILE(s) only txt files!
#
/etc/lircrc.conf


===Installation protocol===
===Installation protocol===
Line 142: Line 173:


Modules in the ''../untestet'' directory must to be customised!
Modules in the ''../untestet'' directory must to be customised!
* One modules requires kernel 2.6
* One modules requires kernel 2.6 (actuator.cmd)
* Some modules are still in beta status
* Some modules are still in beta status
* Other have missing links
* Other have missing links

Revision as of 13:55, 7 December 2004

Description

The Installsscript is a tool that the handles the conventional installation steps with a collection of scripts.

Prerequirements

  • Development environment

Manual

Tutorial

First of all

  • Linux knowledge is required
  • It is useful to have experiences in compiling VDR and it's component manually

Scripts customisation

Decompression

sh vdr-install-script-<VERSION>.run --noexec --target /tmp/VDRtmp
cd /tmp/VDRtmp/setup

It is useful to customise the following configuration file to his own needs

e.g. with the mcedit editor

mcedit config/setup.conf

In ../config/plugins befinden sich die Einstellungen der Plugins, als bsp das audiocd-plugin. ../config/plugins/audiocd.conf

## Description:
#
# -d DEV --device=DEV set device (default: /dev/cdrom)
#
##
-d /dev/cdrom

Options are prefaced with ^-, after selection it goes into the plugin_setup.conf, see pluginsetup-plugin, the same for Description.

## Description: AudioCD Plugin
                ^^^^^^^^^^^^^^
                Würde später im Menu des Plugins (pluginsetup) stehen, ansonnsten <NAME>

Most of the options can be delivered through the commandline, independently from setup.conf

./setup.sh --help
./vdr-install-script-<VERSION>.run -- --help

Backup

In order that the setting are not lost at updates, everything should be backuped.

Execute

./setup.sh

and go to

<-> - Configuration
    | - Load an Alternate Configuration File --->
    | - Save Configuration to an Alternate File --->
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

To save the settings somewhere else, e.g. /media/floppy/.config (ca. 80KB).

After an update, these setting can be loaded through

<-> - Configuration
    | - Load an Alternate Configuration File --->
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Another possibility is the backup of the complete script with

./setup.sh --buildrunpackage
     Label (default "vdr-install-script-<VERSION>.run"):

Gesichert wird, was in ../setup/SAFE definiert wurde.

#
# FILE(s) only txt files!
#
../setup/config/add.conf
#
# DIRECTORY(ies) maxdepth 1, only txt files!
#
../setup/config/plugins

Wer möchte kann auch Files "außerhalb" der Scripts sichern, einfach eintragen.

#
# FILE(s) only txt files!
#
/etc/lircrc.conf

Installation protocol

Startmenu
File:Installscript-02.png
Download Manager
Download Manager
File:Installscript-03.png
DL Manager Sub 1
One layer deeper
File:Installscript-04.png
DL Manager Sub 2
Here, one actually selects the sources
Download status
Startmenu => Software Manager
File:Installscript-07.png
Software Manager
Selection of the packages.
Here, the selection of the sources takes place (version independent). One should roughly what maches together!
Entry for /etc/inittab
Selection of the channels.conf
File:Installscript-11.png
Software Manager
Software Manager => Patches
Basically all patches can be applied as available. Just copy them into ../packages/vdr/patches (requirement: --dry-run works)
If everythings went fine
Mainmenu => Plugins Manager
There are three options: <I> for install, <U> for replace, and <D> for delete. Sometime VDR has to be patched for some plugins, should be visible in the plugins.log, for --reverse of a patches, just de-install the corresponding plugin (<D>).
Show additional options for plugins compilation. See also make.conf
Mainmenu => Compiling
Selection of the DVB driver.
File:Installscript-19.png
Postinstallation
Shows the Postinstallation.
Selection of the options.
Here one can change the options for the compilation of VDR
Show what was compiled
Mainmenu => pluginsetup
Dialog for activation of the plugins, it can later be changed through pluginsetup plugin
File:Installscript-25.png
Installationslog
The log files are located in /var/log/vdr

Scripts

Available modules

This is an index of the available modules. Everything below ./add can be upgraded.

Modules in the ../untestet directory must to be customised!

  • One modules requires kernel 2.6 (actuator.cmd)
  • Some modules are still in beta status
  • Other have missing links

Stow(ES)

GNU stow helps to organise the files under /usr/local, by installing every software under his own directory tree under /usr/local/stow. And then, symbol links create the illusion, every software is installed in the same place.

Here are some of the most important commands

  • help
/usr/local/stow/stowES help --prog stow=/usr/local/stow/stow
  • checkstow (cs)
/usr/local/stow/stowES cs --prog stow=/usr/local/stow/stow
Checking packages in /usr/local/stow (78 matches):
I (  772.5) DFB++-0.9.20
I (  1,385) DirectFB-0.9.20
I (19223.5) ImageMagick-6.0.2
I ( 10,085) MPlayer-1.0pre4
....
  • checkin (ci)
/usr/local/stow/stowES ci MPlayer-1.0pre4 --prog stow=/usr/local/stow/stow
Calling "stow" to check in package MPlayer-1.0pre4 ...done.
Calling ldconfig
  • ceckout (co)
/usr/local/stow/stowES co MPlayer-1.0pre4 --prog stow=/usr/local/stow/stow
Calling "stow -D" to check out package MPlayer-1.0pre4 ...done.
Calling ldconfig.
  • remove (rm)
/usr/local/stow/stowES rm MPlayer-1.0pre4 --prog stow=/usr/local/stow/stow
Calling "stow -D" to check out package MPlayer-1.0pre4 ...done.
Calling "rm -rf" to remove package MPlayer-1.0pre4 ...done.
Calling ldconfig.
  • exchange
/usr/local/stow/stowES exchange MPlayer-1.0pre4 MPlayer-1.0pre5 --prog stow=/usr/local/stow/stow
Calling "stow -D" to check out package MPlayer-1.0pre4 ...done.
Calling "stow" to check in package MPlayer-1.0pre5 ...done.
Calling ldconfig.

To be continued...

Links

[1] ftp://ftp.cadsoft.de/vdr/Tools VDR FTP
[2] http://linvdr.org/download/vdr/Tools Download mirror
[3] http://savannah.gnu.org/projects/stow GNU Stow project homepage
[4] http://www.inf.tu-dresden.de/~al10/stowES Extensions to Stow
[5] http://linuxwiki.de/Stow Stow Wiki