libsystemd-dhcp: Use be32_t for IP addresses in network order.

[elogind.git] / DISTRO_PORTING

diff --git a/DISTRO_PORTING b/DISTRO_PORTING
index 419053832d7b23324492cf31c1fe2e3a5bce15e2..d799e537189993fa2ddfb6c647bac0740734e473 100644 (file)
--- a/DISTRO_PORTING
+++ b/DISTRO_PORTING
@@ -1,36 +1,34 @@
 Porting systemd To New Distributions
 
+HOWTO:
         You need to make the follow changes to adapt systemd to your
         distribution:
 
-        0) Make your distribution recognized via the autoconf checks
-        in configure.ac. Grep for the word "fedora" (case
-        insensitively) and you should be able to find the places where
-        you need to add/change things.
+        1) Find the right configure parameters for:
 
-        1) Patch src/hostname-setup.c so that systemd knows where to
-        read your host name from.
+            --with-rootprefix=
+            --with-sysvinit-path=
+            --with-sysvrcnd-path=
+            --with-rc-local-script-path-start=
+            --with-rc-local-script-path-stop=
+            --with-kbd-loadkeys=
+            --with-kbd-setfont=
+            --with-tty-gid=
 
-        2) Check the unit files in units/ if they match your
-        distribution. Most likely you will have to make additions to
-        units/*.m4 and create a copy of units/fedora/ with changes for
-        your distribution.
-
-        3) Adjust Makefile.am to register the unit files you added in
-        step 2. Also you might need to update the m4 invocation in
-        Makefile.am. Grep for the word "fedora" (case insensitively)
-        and you should be able to find the places where you need to
-        add/change things.
-
-        4) Try it out.
+        2) Try it out. Play around with 'systemd --test --system' for
+        a test run of systemd without booting. This will read the unit
+        files and print the initial transaction it would execute
+        during boot-up. This will also inform you about ordering loops
+        and suchlike.
 
 CONTRIBUTING UPSTREAM:
 
-        We are interested in merging your changes upstream, if they
-        are for a big, and well-known distribution. Unfortunately we
-        don't have the time and resources to maintain
-        distribution-specific patches for all distributions on the
-        planet, hence please do not send us patches that adds systemd
-        support to non-mainstream or niche distributions.
+        We do generally no longer accept distribution-specific
+        patches to systemd upstream. If you have to make changes to
+        systemd's source code to make it work on your distribution:
+        unless your code is generic enough to be generally useful, we
+        are unlikely to merge it. Please always consider adopting the
+        upstream defaults. If that is not possible, please maintain
+        the relevant patches downstream.
 
         Thank you for understanding.