diff options
| author | V3n3RiX <venerix@redcorelinux.org> | 2019-12-15 18:09:03 +0000 |
|---|---|---|
| committer | V3n3RiX <venerix@redcorelinux.org> | 2019-12-15 18:09:03 +0000 |
| commit | 7bc9c63c9da678a7e6fceb095d56c634afd22c56 (patch) | |
| tree | 4a67d50a439e9af63947e5f8b6ba3719af98b6c9 /eclass/savedconfig.eclass | |
| parent | b284a3168fa91a038925d2ecf5e4791011ea5e7d (diff) | |
gentoo resync : 15.12.2019
Diffstat (limited to 'eclass/savedconfig.eclass')
| -rw-r--r-- | eclass/savedconfig.eclass | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/eclass/savedconfig.eclass b/eclass/savedconfig.eclass index dab2283fe0f4..8f64c5b8edd0 100644 --- a/eclass/savedconfig.eclass +++ b/eclass/savedconfig.eclass @@ -14,20 +14,20 @@ # so users can modify these config files and the ebuild will take it # into account as needed. # -# @ROFF .nr step 1 1 +# @ROFF .nr R 1 1 # Typically you can create your own configuration files quickly by # doing: -# @ROFF .IP \n[step] 3 +# @ROFF .IP \nR 3 # Build the package with FEATURES=noclean USE=savedconfig. -# @ROFF .IP \n+[step] +# @ROFF .IP \n+R # 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+[step] +# @ROFF .IP \n+R # Copy the modified configuration files out of the workdir and to # the paths in /etc/portage/savedconfig/. -# @ROFF .IP \n+[step] +# @ROFF .IP \n+R # Emerge the package with just USE=savedconfig to get the custom build. inherit portability |