Remove all @ROFF tokens, because they make conversion to any format other than a man page very difficult. Replace the numbered list by explicitly numbered paragraphs.
Signed-off-by: Ulrich Müller <u...@gentoo.org> --- eclass/savedconfig.eclass | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/eclass/savedconfig.eclass b/eclass/savedconfig.eclass index 8f64c5b8edd..e90a9b618d6 100644 --- a/eclass/savedconfig.eclass +++ b/eclass/savedconfig.eclass @@ -1,4 +1,4 @@ -# Copyright 1999-2019 Gentoo Authors +# Copyright 1999-2020 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 # @ECLASS: savedconfig.eclass @@ -14,21 +14,21 @@ # so users can modify these config files and the ebuild will take it # into account as needed. # -# @ROFF .nr R 1 1 # Typically you can create your own configuration files quickly by # doing: -# @ROFF .IP \nR 3 -# Build the package with FEATURES=noclean USE=savedconfig. -# @ROFF .IP \n+R -# Go into the build dir and edit the relevant configuration system +# +# 1. Build the package with FEATURES=noclean USE=savedconfig. +# +# 2. Go into the build dir and edit the relevant configuration system # (e.g. `make menuconfig` or `nano config-header.h`). You can look # at the files in /etc/portage/savedconfig/ to see what files get # loaded/restored. -# @ROFF .IP \n+R -# Copy the modified configuration files out of the workdir and to +# +# 3. Copy the modified configuration files out of the workdir and to # the paths in /etc/portage/savedconfig/. -# @ROFF .IP \n+R -# Emerge the package with just USE=savedconfig to get the custom build. +# +# 4. Emerge the package with just USE=savedconfig to get the custom +# build. inherit portability -- 2.25.1
signature.asc
Description: PGP signature
