Browse Source

Merge branch 'master' of git.devuan.org:devuan/documentation

wip/leepen/libsystemd0
fsmithred 7 months ago
parent
commit
54e9683916
  1. BIN
      art/graphics/chimaera-deepsea/Clearlooks-Phenix-Deepsea.tar.gz
  2. BIN
      art/graphics/logo/devuan-logo.png
  3. 2
      maintainers/JenkinsAutobuild.md
  4. 21
      maintainers/PackagingGuide.md
  5. 2
      maintainers/README.md

BIN
art/graphics/chimaera-deepsea/Clearlooks-Phenix-Deepsea.tar.gz

Binary file not shown.

BIN
art/graphics/logo/devuan-logo.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.2 KiB

2
maintainers/JenkinsAutobuild.md

@ -40,4 +40,4 @@ pipeline](https://jenkins.devuan.dev/job/devuan-package-builder/) (no login
needed) where you can follow the progress of your build.
The Jenkins Pipeline also sends notifications to the #devuan-ci channel on
irc.freenode.net.
irc.libera.chat.

21
maintainers/PackagingGuide.md

@ -15,15 +15,15 @@ starting points:-
Devuan's source code is maintained in [git](https://git.devuan.org), builds are
performed using [jenkins](https://jenkins.devuan.dev), package repositories are
maintained with [dak](https://git.devuan.org/devuan-infrastructure/dak) and
maintained with [dak](https://git.devuan.org/devuan/dak) and
those repositories are merged with Debian's to produce the distribution by
[amprolla](https://git.devuan.org/devuan-infrastructure/amprolla3).
[amprolla](https://git.devuan.org/devuan/amprolla3).
The majority of Devuan's packages are used directly from Debian with no
recompilation. Only packages that require modification are forked and rebuilt.
Packaging help can be found by asking on the #devuan-dev channel on
irc.freenode.net.
irc.libera.chat.
## Infrastructure
@ -52,6 +52,12 @@ There are four categories of packages in Devuan:-
elogind and eudev).
4. Used directly from Debian unchanged.
In general, packages in category 2 are forked so they work on Devuan with
non-systemd init systems. Note that the current policy is *not* to fork a
package only to remove systemd unit files and/or libsystemd0
dependencies. Further details on this and the rationale behind it can be found in
this [forum post by KatolaZ](https://dev1galaxy.org/viewtopic.php?id=1925).
Packages in the last category will usually not be present in Devuan's git or
jenkins. However, packages can change category over time and so remnants of
previous incarnations may remain.
@ -64,8 +70,13 @@ previous incarnations may remain.
Package Tracker](https://tracker.debian.org). This is optional, but makes
merging much easier and is encouraged.
3. Create a new branch from your chosen starting point. This is usually the
version in Debian unstable. rmadison(1) from the devscripts package is a
convenient way of determining current Debian versions.
version in Debian unstable.
rmadison(1) from the devscripts package is a convenient way of determining
current versions. By default it lists Debian packages. To query Devuan's
pacakges add
```RMADISON_URL_MAP_DEVUAN=https://api.pkginfo.devuan.org/madison``` to
`~/.devscripts` and invoke rmadison with `-u devuan` switch.
Usually packages are initially built for unstable or experimental so the
branch should be named suites/unstable or suites/experimental accordingly.

2
maintainers/README.md

@ -2,7 +2,7 @@
There is no formal procedure to become a Devuan contributor. A good starting
place is to join the conversations on the #devuan-dev channel at
irc.freenode.net and subscribe to the [Devuan Developers
irc.libera.chat and subscribe to the [Devuan Developers
list](https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/devuan-dev). The
community will be interested to hear your ideas, experience and the ways in
which you wish to contribute. There is also a weekly meeting (currently Thursday

Loading…
Cancel
Save