Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/rst0git/p4lang-packages
P4 Packages
https://github.com/rst0git/p4lang-packages
debian linux p4 ubuntu
Last synced: about 6 hours ago
JSON representation
P4 Packages
- Host: GitHub
- URL: https://github.com/rst0git/p4lang-packages
- Owner: rst0git
- Created: 2021-11-27T09:43:31.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2024-02-13T14:49:57.000Z (11 months ago)
- Last Synced: 2024-11-08T08:07:22.962Z (about 2 months ago)
- Topics: debian, linux, p4, ubuntu
- Language: Makefile
- Homepage:
- Size: 66.4 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
[](https://build.opensuse.org/package/show/home:p4lang/p4lang-p4c)
[](https://build.opensuse.org/package/show/home:p4lang/p4lang-bmv2)
[](https://build.opensuse.org/package/show/home:p4lang/p4lang-pi)
# P4 Packages
This repository contains all files necessary to build packages for Ubuntu and Debian.
To build all debian packages run inside Ubuntu 20.04 container using Docker run the
following script:
```bash
./build.sh
```
## Build dependencies
Note that `build.sh` requires [Podman](https://podman.io/getting-started/installation.html) or [Docker](https://docs.docker.com/engine/install/) to be pre-installed.
# Ubuntu/Debian
Building a package for Ubuntu or Debian requires a number of files to be added in a subdirectory directory, called `debian`, in the source tree. These files can be used to build two types of packages: binary packages and source packages.
Binary packages contain executables, configuration files, man pages, copyright information, and other documentation. They can be installed on Ubuntu/Debian system with `dpkg` or `apt-get`.
In contrast, source packages contain the original unmodified source code in gzip-compressed tar format, a file describing the source package, and usually a file that contains changes to the original source. Source packages are used by automated build systems such as [Launchpad](https://launchpad.net/) and [Open Build Service](https://openbuildservice.org/).
## Building packages
The following commands can be used to build a Debian/Ubuntu package manually.
### Binary package
This command creates a `.deb` file.
```bash
dpkg-buildpackage -us -uc
```
### Source package
This command creates a source package for a new version of the source code file (`.orig.tar.gz`).
```bash
debuild -sa
```
### Source package update
This command creates an update for source package with an existing source code file (`.orig.tar.gz`).
```bash
debuild -sd
```
## Files under the `debian` directory
### `control`
This file contains [control information](https://www.debian.org/doc/debian-policy/ch-controlfields.html) used by package management tools.
### `rules`
This is an executable Makefile that is used to create the package. Like any other Makefile, it consists of several rules, each of which defines a target and how it is carried out.
### `changelog`
This file contains a brief explanation of changes and updates to the package.
### `copyright`
This file contains information about the copyright and license of the upstream sources.
### `compat`
This file specifies the [compatibility level](https://manpages.debian.org/bullseye/debhelper/debhelper.7.en.html#COMPATIBILITY_LEVELS) for the [debhelper](https://packages.debian.org/search?keywords=debhelper) tool.
### `source/format`
This file contains the version number for the format of the source package.