From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Maxin John <maxin.john@gmail.com>
Subject: [nanbield][PATCH 4/7] ref-manual: classes: remove insserv bbclass
Date: Fri, 12 Jan 2024 17:50:56 +0100 [thread overview]
Message-ID: <20240112165059.3553847-5-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20240112165059.3553847-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
From: Maxin B. John <maxin.john@gmail.com>
insserv.bbclass was removed from oe-core:
commit e6bb5dbb62257a7de730ea9085dfd89520f3e47d
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Sun May 10 12:30:49 2015 +0100
insserv: Remove
Signed-off-by: Maxin John <maxin.john@gmail.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/ref-manual/classes.rst | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
index a8afe9f2dc..8d8bea4714 100644
--- a/documentation/ref-manual/classes.rst
+++ b/documentation/ref-manual/classes.rst
@@ -1538,16 +1538,6 @@ Here are the tests you can list with the :term:`WARN_QA` and
automatically get these versions. Consequently, you should only need
to explicitly add dependencies to binary driver recipes.
-.. _ref-classes-insserv:
-
-``insserv``
-===========
-
-The :ref:`ref-classes-insserv` class uses the ``insserv`` utility to update the order
-of symbolic links in ``/etc/rc?.d/`` within an image based on
-dependencies specified by LSB headers in the ``init.d`` scripts
-themselves.
-
.. _ref-classes-kernel:
``kernel``
--
2.34.1
next prev parent reply other threads:[~2024-01-12 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 16:50 [nanbield][PATCH 0/7] documentation backports michael.opdenacker
2024-01-12 16:50 ` [nanbield][PATCH 1/7] dev-manual: start.rst: Update use of Download page michael.opdenacker
2024-01-12 16:50 ` [nanbield][PATCH 2/7] contributor-guide: use "apt" instead of "aptitude" michael.opdenacker
2024-01-12 16:50 ` [nanbield][PATCH 3/7] dev-manual: update license manifest path michael.opdenacker
2024-01-12 16:50 ` michael.opdenacker [this message]
2024-01-12 16:50 ` [nanbield][PATCH 5/7] manuals: document VSCode extension michael.opdenacker
2024-01-12 16:50 ` [nanbield][PATCH 6/7] documentation: Add UBOOT_BINARY, extend UBOOT_CONFIG michael.opdenacker
2024-01-12 16:50 ` [nanbield][PATCH 7/7] migration-guide: add release notes for 4.3.2 michael.opdenacker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240112165059.3553847-5-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=maxin.john@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox