File: README.source

package info (click to toggle)
firmware-nonfree 0.43
  • links: PTS, VCS
  • area: non-free
  • in suites: jessie, jessie-kfreebsd
  • size: 49,736 kB
  • ctags: 42
  • sloc: python: 392; sh: 203; makefile: 43
file content (82 lines) | stat: -rw-r--r-- 3,024 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
firmware-nonfree
================

Source format
-------------

firmware-nonfree is a native package even though the installed files
are neither Debian-specific nor developed by Debian.  This is done
because it is built from multiple 'upstream' sources, most of which do
not make tarball releases.

Binary package definition
-------------------------

The binary package definitions are written in a format similar to INI
files, parsed using the Python ConfigParser module
<http://docs.python.org/release/2.7/library/configparser.html>,

The [base] packages field in the top-level 'defines' file lists all
the binary package names, without the fixed prefix 'firmware-'.

For each binary package, there is a subdirectory with matching name
(again without the prefix) containing the binary files that will be
installed in it and another 'defines' file with metadata.

Required metadata:

[base] desc: Short description of related hardware, used in Description
[base] files: List of files to be included, one per line
[base] longdesc: Longer description of related hardware and drivers, used in
                 Description.
[base] uri: Upstream URL, used as Homepage and in copyright file

Optional metadata:

[base] license-accept: Set to 'required' if we must prompt the user to
                       accept a EULA on installation
[base] license-title: Title of the EULA
[base] support: Set to 'initramfs-tools' if update-initramfs should be
                invoked after installation
[base] replaces: Used as Replaces field
[base] conflicts: Used as Conflicts field
[base] provides: Used as Provides field

Optional per-file metadata:

[<filename>_base] desc: One-line description for this file, used in
                        package description
[<filename>_base] version: Verson number for this file, used in package
                           description

To re-generate debian/control (and other files) based on these
definitions:

1. Install the current linux-support-<kernelversion> package
2. Ensure debian/rules.defs has the right value of KERNELVERSION
3. Run: debian/rules debian/control

Upstream
--------

The main upstream source is the linux-firmware.git repository, but
some binary packages are based on other sources as specified by the
[base] uri field in the 'defines' file in the package subdirectory.

You can compare the current files with a checkout of that repository
using the script 'debian/bin/check_upstream.py'.  This ignores files
with unclear or unrecognised licences, and as specified in the
[upstream] exclude field of the top-level 'defines' file.

Licences
--------

Each binary package is assumed to have a different licence(s).  The
installed 'copyright' file is taken from the 'LICENSE' file in its
subdirectory.

Some firmware redistribution licences require us to prompt the user to
accept an EULA.  In this case, put the EULA text in 'LICENSE.install'
and set the [base] license-accept field to 'required'.

 -- Ben Hutchings <ben@decadent.org.uk>, Sun, 24 Jun 2012 22:56:20 +0100