Meta package for the Regolith Desktop Environment
This is the meta-package for Regolith Linux that bundles all custom packages into a common root. The package is just a container, and contains no files or logic itself.
This guide assumes you wish to make changes to a Regolith package and host those changes in a new version. It also assumes you'll be building from an Ubuntu-based system like Regolith and you already have setup the Debian package tools. See this concise guide to install the tools and get a familiar with the workflow.
This step will pull the Regolith package metadata down from GitHub. The debian metadata is on a branch called
debian, due to conflicts that this README presents to the build tool.
git clone -b debian https://github.com/regolith-linux/regolith-desktop
Now we will build the package locally and generate the Debian package metadata required for hosting in a Private Package Archive (PPA).
debuild -S -sa
There should now be a number of files generated in the parent directory, such as
It's necessary to update the version of the package so that the local package manager will be able to determine that an update is available. The Debian packaging tools provide the program
dchfor this task.
debian/changelogfile. This file contains the package versioning metadata and is organized by stanzas of three elements: version, change info, and author of change. It's similiar in a way to a git commit log + release tags, but managed in a file rather than the git index. Run
dchand update the version string, change UNRELEASED to your intended Ubuntu version target (probably
bionic) and then below add a description of your change. The rest should be done automatically by the
dchprogram. Verify that your change follows the pattern of entries below it.
You may wish to change the package version in the
debian\changelogfile to avoid conflicts, but that is optional and up to you.
dput ppa:/// ../regolith-desktop_2.07-1ubuntu1_source.changes
After uploading the package to your PPA, you should get an email from Launchpad.net regarding if the package was accepted or rejected. Then, some time later the package should have been build and available for installation. Assuming you have already added your PPA via
sudo apt updateand
sudo apt upgradeshould cause the new package to be installed on your local system.
This project exists thanks to all the people who contribute. [Contribute].
Become a financial contributor and help us sustain our community. [Contribute]
Support this project with your organization. Your logo will show up here with a link to your website. [Contribute]