public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Frysinger (vapier)" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in eclass: savedconfig.eclass
Date: Mon, 28 Jan 2013 20:11:14 +0000 (UTC)	[thread overview]
Message-ID: <20130128201114.D30DF2171D@flycatcher.gentoo.org> (raw)

vapier      13/01/28 20:11:14

  Modified:             savedconfig.eclass
  Log:
  add high level over view of how to use this eclass for users

Revision  Changes    Path
1.21                 eclass/savedconfig.eclass

file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/savedconfig.eclass?rev=1.21&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/savedconfig.eclass?rev=1.21&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/savedconfig.eclass?r1=1.20&r2=1.21

Index: savedconfig.eclass
===================================================================
RCS file: /var/cvsroot/gentoo-x86/eclass/savedconfig.eclass,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- savedconfig.eclass	4 Jan 2012 08:23:51 -0000	1.20
+++ savedconfig.eclass	28 Jan 2013 20:11:14 -0000	1.21
@@ -1,6 +1,6 @@
 # Copyright 1999-2011 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/eclass/savedconfig.eclass,v 1.20 2012/01/04 08:23:51 vapier Exp $
+# $Header: /var/cvsroot/gentoo-x86/eclass/savedconfig.eclass,v 1.21 2013/01/28 20:11:14 vapier Exp $
 
 # @ECLASS: savedconfig.eclass
 # @MAINTAINER:
@@ -13,6 +13,22 @@
 # of saving and restoring the configuration files was developed
 # so users can modify these config files and the ebuild will take it
 # into account as needed.
+#
+# @ROFF .nr step 1 1
+# Typically you can create your own configuration files quickly by
+# doing:
+# @ROFF .IP \n[step] 3
+# Build the package with FEATURES=noclean USE=savedconfig.
+# @ROFF .IP \n+[step]
+# 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]
+# Copy the modified configuration files out of the workdir and to
+# the paths in /etc/portage/savedconfig/.
+# @ROFF .IP \n+[step]
+# Emerge the package with just USE=savedconfig to get the custom build.
 
 inherit portability
 





             reply	other threads:[~2013-01-28 20:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 20:11 Mike Frysinger (vapier) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-01-04  8:23 [gentoo-commits] gentoo-x86 commit in eclass: savedconfig.eclass Mike Frysinger (vapier)
2012-01-04  7:45 Mike Frysinger (vapier)
2012-01-04  6:22 Mike Frysinger (vapier)
2012-01-04  6:19 Mike Frysinger (vapier)
2011-07-26 17:35 Zac Medico (zmedico)
2010-10-05 19:51 Mike Frysinger (vapier)
2010-03-08  4:32 Jeroen Roovers (jer)
2009-10-30 16:46 Mike Frysinger (vapier)
2009-10-30  0:05 Mike Frysinger (vapier)
2009-04-11 15:19 Mike Frysinger (vapier)
2008-03-20 16:23 Torsten Veller (tove)

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=20130128201114.D30DF2171D@flycatcher.gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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