summaryrefslogtreecommitdiff
path: root/debian/control
diff options
context:
space:
mode:
Diffstat (limited to 'debian/control')
-rw-r--r--debian/control36
1 files changed, 36 insertions, 0 deletions
diff --git a/debian/control b/debian/control
new file mode 100644
index 0000000..3887e06
--- /dev/null
+++ b/debian/control
@@ -0,0 +1,36 @@
+Source: dmidecode
+Section: utils
+Priority: optional
+Maintainer: Jörg Frings-Fürst <debian@jff.email>
+Build-Depends: debhelper-compat (= 13)
+Standards-Version: 4.6.0.0
+Rules-Requires-Root: no
+Vcs-Git: git://jff.email/opt/git/dmidecode.git
+Vcs-Browser: https://jff.email/cgit/dmidecode.git/
+Homepage: https://nongnu.org/dmidecode/
+
+Package: dmidecode
+Priority: important
+Architecture: any-amd64 arm64 armhf ia64 any-i386 riscv64
+Multi-Arch: foreign
+Depends: ${misc:Depends}, ${shlibs:Depends}
+Description: SMBIOS/DMI table decoder
+ Dmidecode reports information about the system's hardware as described in the
+ system BIOS according to the SMBIOS/DMI standard.
+ .
+ This information typically includes system manufacturer, model name, serial
+ number, BIOS version, asset tag as well as a lot of other details of varying
+ level of interest and reliability depending on the manufacturer. This will
+ often include usage status for the CPU sockets, expansion slots (e.g. AGP, PCI,
+ ISA) and memory module slots, and the list of I/O ports (e.g. serial, parallel,
+ USB).
+ .
+ Beware that DMI data have proven to be too unreliable to be blindly trusted.
+ Dmidecode does not scan the hardware, it only reports what the BIOS told it to.
+
+Package: dmidecode-udeb
+Section: debian-installer
+Architecture: any-amd64 arm64 armhf ia64 any-i386
+Package-Type: udeb
+Depends: ${misc:Depends}, ${shlibs:Depends}
+Description: SMBIOS/DMI table decoder (udeb)