fwupd/contrib
Richard Hughes cf8095d5af Use a static version number
Getting the version string from git means the commit version changes each time
we commit any patch, which means we need to use --force to install firmware
when building fwupd against a version that should be compatible.

It is also very inconvenient not bumping the release version for git snapshots
as firmware can no longer depend on the "planned" release triplet.

tl;dr: A good idea for Flashrom, not so awesome for me.
2020-03-29 12:17:52 +01:00
..
ci Use a static version number 2020-03-29 12:17:52 +01:00
debian Use Jcat files in firmware archives and for metadata 2020-03-23 19:55:12 +00:00
firmware_packager Add a helper script to add a DFU header 2020-03-09 21:12:01 +00:00
flatpak@3e60bea4e7 contrib: Adjust flatpak build for moving to flathub 2018-11-01 06:51:23 -05:00
snap trivial: snap: fix bash completion 2020-03-20 11:18:00 -05:00
standalone-installer trivial: fixup standalone installer 2019-08-06 09:58:26 +01:00
vscode contrib: Add information on how to use debugging scripts 2018-10-11 07:43:56 -05:00
afl-fuzz.py Use parallel fuzzing for the SMBIOS checks too 2019-10-02 16:28:28 +01:00
fix_translations.py Remove the autogenerated headers in the gettext files 2019-02-01 14:25:26 +00:00
fwupd.spec.in Use a static version number 2020-03-29 12:17:52 +01:00
generate-version-script.py trivial: Fix the version generator to correctly compare versions 2020-02-24 18:49:22 +00:00
meson.build Generate a win32 setup binary 2020-01-16 12:23:08 -06:00
mingw64.cross Allow building on Windows with MinGW 2019-12-03 16:33:43 +00:00
nvme-parse.py trivial: Add the script used to generate the NVMe stats 2018-09-04 20:37:17 +01:00
PKGBUILD Use a static version number 2020-03-29 12:17:52 +01:00
README.md trivial: contrib: Update README for proper docker command (Closes: #615) 2018-08-09 13:22:29 +01:00
setup-win32.nsi Use Jcat files in firmware archives and for metadata 2020-03-23 19:55:12 +00:00

Distribution packages

The relevant packaging necessary to generate RPM, DEB and PKG distribution packages is contained here. It is used regularly for continuous integration using Travis CI. The generated packages can be used on a distribution such as Fedora, Debian, Ubuntu or Arch Linux.

The build can be performed using Linux containers with Docker.

RPM packages

A Dockerfile for Fedora can be generated in contrib.

To prepare the Docker container run this command:

OS=fedora ./generate_docker.py

To build the RPMs run this command (from the root of your git checkout):

docker run --privileged -t -v `pwd`:/build fwupd-fedora

RPMs will be made available in your working directory when complete.

DEB packages

A Dockerfile for Debian or Ubuntu can be generated in contrib.

To prepare the Docker container run one of these commands:

OS=debian-x86_64 ./generate_docker.py
OS=debian-i386 ./generate_docker.py
OS=ubuntu-x86_64 ./generate_docker.py

To build the DEBs run one of these commands (from the root of your git checkout):

docker run --privileged -t -v `pwd`:/build fwupd-debian-x86_64
docker run --privileged -t -v `pwd`:/build fwupd-debian-i386
docker run --privileged -t -v `pwd`:/build fwupd-ubuntu-x86_64

DEBs will be made available in your working directory when complete.

PKG packages

A Dockerfile for Arch can be generated in contrib.

To prepare the Docker container run this command:

OS=arch ./generate_docker.py

To build the PKGs run this command (from the root of your git checkout):

docker run -t -v `pwd`:/build fwupd-arch

PKGs will be made available in your working directory when complete.

Additional packages

Submissions for generating additional packages for other distribution mechanisms are also welcome.
All builds should occur in Docker containers.

Please feel free to submit the following:

  • Dockerfile for the container for your distro
  • Relevant technical packaging scripts (such as ebuilds, spec file etc)
  • A shell script that can be launched in the container to generate distribution packages