fix note about officially supported archs #54515

1 files changed, 16 insertions, 16 deletions

diff --git a/skel.ebuild b/skel.ebuild
index ce262a9c5ea1..f6c50546f6f5 100644
--- a/skel.ebuild
+++ b/skel.ebuild
@@ -2,7 +2,7 @@
 # Distributed under the terms of the GNU General Public License v2
 # $Header: $
 
-# NOTE: The comments in this file are for instruction and documentation.
+# NOTE: The comments in this file are for instruction and documentation.  
 # They're not meant to appear with your final, production ebuild.  Please
 # remember to remove them before submitting or committing your ebuild.  That
 # doesn't mean you can't add your own comments though.
@@ -21,16 +21,16 @@ HOMEPAGE="http://foo.bar.com/"
 # Portage.
 SRC_URI="ftp://foo.bar.com/${P}.tar.gz"
 
-# License of the package. This must match the name of file(s) in
-# /usr/portage/licenses/. For complex license combination see the developer
+# License of the package.  This must match the name of file(s) in
+# /usr/portage/licenses/.  For complex license combination see the developer
 # docs on gentoo.org for details.
 LICENSE=""
 
 # The SLOT variable is used to tell Portage if it's OK to keep multiple
-# versions of the same package installed at the same time. For example,
+# versions of the same package installed at the same time.  For example,
 # if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible
 # with 1.2.2), it would be optimal to instruct Portage to not remove
-# libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this,
+# libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2.  To do this,
 # we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2.
 # emerge clean understands SLOTs, and will keep the most recent version
 # of each SLOT and remove everything else.
@@ -40,28 +40,28 @@ LICENSE=""
 SLOT="0"
 
 # Using KEYWORDS, we can record masking information *inside* an ebuild
-# instead of relying on an external package.mask file. Right now, you
+# instead of relying on an external package.mask file.  Right now, you
 # should set the KEYWORDS variable for every ebuild so that it contains
-# the names of all the architectures with which the ebuild works. We have
-# 4 official architecture names right now: "~x86", "~ppc", "~sparc"
-# and "~alpha".  The ~ in front of the architecture indicates that the
-# package is new and should be considered unstable until testing proves its
-# stability.  Once packages go stable the ~ prefix is removed.
-# So, if you've confirmed that your ebuild works on x86 and ppc,
-# you'd specify: KEYWORDS="~x86 ~ppc"
+# the names of all the architectures with which the ebuild works.  All of
+# the official architectures can be found in the keywords.desc file which 
+# is in /usr/portage/profiles/.  Usually you should just set this to "~x86".  
+# The ~ in front of the architecture indicates that the package is new and 
+# should be considered unstable until testing proves its stability.  Once 
+# packages go stable the ~ prefix is removed.  So, if you've confirmed that 
+# your ebuild works on x86 and ppc, you'd specify: KEYWORDS="~x86 ~ppc"
 # For packages that are platform-independent (like Java, PHP or Perl
 # applications) specify all keywords.
 # For binary packages, use -* and then list the archs the bin package
 # exists for.  If the package was for an x86 binary package, then
 # KEYWORDS would be set like this: KEYWORDS="-* x86"
-# DO NOT USE KEYWORDS="*". This is deprecated and only for backward
+# DO NOT USE KEYWORDS="*".  This is deprecated and only for backward
 # compatibility reasons.
 KEYWORDS="~x86"
 
 # Comprehensive list of any and all USE flags leveraged in the ebuild,
 # with the exception of any ARCH specific flags, i.e. "ppc", "sparc",
-# "x86" and "alpha". This is a required variable. If the
-# ebuild doesn't use any USE flags, set to "".
+# "x86" and "alpha".  This is a required variable.  If the ebuild doesn't 
+# use any USE flags, set to "".
 IUSE="X gnome"
 
 # Build-time dependencies, such as