Cucumber Linux Wiki

devdocs:update_package

z5t1 (z5t1@undisclosed.example.com) — 2019-01-24T21:02:47+0000

The following is the process for building and releasing an updated package using the build infrastructure. Throughout this guide, substitute the version of Cucumber Linux you are building in for x.y. On the staging server: * Update the ports tree:

devdocs:start - [Maintainer's Guide]

z5t1 (z5t1@undisclosed.example.com) — 2019-01-24T17:06:12+0000

Development Documents This section is where the Cucumber Linux development documents and plans are outlined. If you are new to contributing to Cucumber Linux or would like to start contributing, looking at the To Do List is a great place to start. Active Subpages

devdocs:deploy_new_build_server

z5t1 (z5t1@undisclosed.example.com) — 2019-01-07T17:12:52+0000

Deploying a New Build Server The following is the process for deploying a new build server. * Edit the /etc/pickle.conf file and set MIRROR variable to point to the staging server. * Install the the build server buildtools (substitute the version number of Cucumber Linux you are building in for

package_management - [Setting up Pickle]

z5t1 (z5t1@undisclosed.example.com) — 2018-12-31T16:28:33+0000

Package Management Cucumber Linux uses Slackware's package management scripts. Documentation regarding them can be found at . Update Management The update manager for Cucumber Linux is called the Package Installer for Cucumber Kernels, Libraries and Executables (or Pickle for short). This is a simple shell script that attempts to manage the system updates for you. It isn't completely stable yet, so it is a good idea to also keep an eye on the chan…

references:uids - [User IDs]

z5t1 (z5t1@undisclosed.example.com) — 2018-12-21T18:35:54+0000

User IDs The following table contains a list of all the currently used User IDs on Cucumber Linux UID User Primary Group Description 0 root 0 (root) root 1 bin 1 (bin)

devdocs:finalize_release_process

z5t1 (z5t1@undisclosed.example.com) — 2018-12-03T16:52:51+0000

Release Process Updated November 17, 2018 The following is the process for finalizing a new release of Cucumber Linux. The first part of the release process differs depending on whether you are releasing from a build server of a bootstrap server. If you are completing a Cucumber Linux from Scratch build, then you are releasing from a bootstrap server. Otherwise, you are releasing from a build server.

devdocs:sysbuild_numbers - [Build Number List]

z5t1 (z5t1@undisclosed.example.com) — 2018-11-18T14:05:06+0000

Build Numbers Every time Cucumber Linux is rebuilt from scratch, a new system build number (called sysbuild number) is assigned to that build. This is done due to the fact that each new build has the potential to break ABI compatibility. Using these build numbers makes it easy to keep track which ABI revision a system is on.

logo.png - created

z5t1 (z5t1@undisclosed.example.com) — 2018-08-30T22:43:07+0000