[gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/

public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed

From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/
Date: Fri, 28 Oct 2016 17:13:54 +0000 (UTC)	[thread overview]
Message-ID: <1477674810.3607b7a4e355a2421321f2dfccc24f40f1d0d48e.ulm@gentoo> (raw)

commit:     3607b7a4e355a2421321f2dfccc24f40f1d0d48e
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 28 17:13:30 2016 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri Oct 28 17:13:30 2016 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=3607b7a4

Whitespace fixes.

 ebuild-writing/common-mistakes/text.xml | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/ebuild-writing/common-mistakes/text.xml b/ebuild-writing/common-mistakes/text.xml
index 8293bc8..1a2ef85 100644
--- a/ebuild-writing/common-mistakes/text.xml
+++ b/ebuild-writing/common-mistakes/text.xml
@@ -237,7 +237,7 @@ part.
   </li>
   <li>
     <e>One dependency per line.</e><br />
-    Don't put multiple dependency on the same line. It makes it ugly to read 
+    Don't put multiple dependency on the same line. It makes it ugly to read
     and hard to follow.
   </li>
 </ul>
@@ -293,17 +293,17 @@ some tips on how to find the correct dependencies.
 
 <p>
 Another common mistake users make when submitting ebuilds is supplying an
-invalid license. For example, <c>GPL</c> is not a valid license. You need to 
-specify <c>GPL-1</c> or <c>GPL-2</c>. Same with <c>LGPL</c>. Make sure the 
-license you use in the <c>LICENSE</c> field is something that exists in 
-<path>/usr/portage/licenses</path>. As a tip, check the <path>COPYING</path> 
+invalid license. For example, <c>GPL</c> is not a valid license. You need to
+specify <c>GPL-1</c> or <c>GPL-2</c>. Same with <c>LGPL</c>. Make sure the
+license you use in the <c>LICENSE</c> field is something that exists in
+<path>/usr/portage/licenses</path>. As a tip, check the <path>COPYING</path>
 in a source tarball for the license. If a package does not specify it
 uses <c>GPL-1</c> or <c>GPL-2</c>, it is very likely it uses <c>GPL-2</c>.
 </p>
 
 <p>
 If the license for the package you submit is unique and not in
-<path>/usr/portage/licenses/</path>, then you must submit the new license in a 
+<path>/usr/portage/licenses/</path>, then you must submit the new license in a
 separate file.
 </p>
 
@@ -377,8 +377,8 @@ tell you if there is trailing whitespace at the end of lines or on empty lines.
 <body>
 
 <p>
-If <c>S=${WORKDIR}/${P}</c>, then you should not add it to your ebuild. This is 
-implied already, you should only add it if it is something other than 
+If <c>S=${WORKDIR}/${P}</c>, then you should not add it to your ebuild. This is
+implied already, you should only add it if it is something other than
 <c>${WORKDIR}/${P}</c>.
 </p>

next             reply	other threads:[~2016-10-28 17:13 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 17:13 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-24 14:15 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/ Ulrich Müller
2022-01-22 23:43 Sam James
2021-12-22 15:38 Ulrich Müller
2021-09-17  9:09 Ulrich Müller
2021-08-14 10:00 Ulrich Müller
2021-08-01  2:43 Sam James
2021-08-01  2:38 Sam James
2021-08-01  2:38 Sam James
2021-08-01  2:38 Sam James
2021-08-01  2:38 Sam James
2021-08-01  2:38 Sam James
2021-03-30 18:20 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-21  6:06 Ulrich Müller
2021-02-06 10:35 Ulrich Müller
2017-01-25  5:31 Göktürk Yüksek
2017-01-25  5:31 Göktürk Yüksek
2017-01-21 19:21 Göktürk Yüksek
2016-02-05 12:59 Ulrich Müller
2014-10-18 17:36 Markos Chandras
2014-05-13 19:32 Ulrich Müller
2013-09-28 12:19 Markos Chandras
2012-12-30 14:21 Julian Ospald
2012-12-04 19:26 Julian Ospald
2012-11-23 18:02 Julian Ospald
2012-11-17 19:00 Markos Chandras
2012-11-11 19:33 Markos Chandras
2012-11-07 13:27 Michael Palimaka
2012-11-07 13:25 Michael Palimaka
2012-08-08 19:20 Markos Chandras
2011-03-09 16:42 Jeremy Olexa

find likely ancestor, descendant, or conflicting patches for this message:
( dfblob:8293bc8 dfblob:1a2ef85 )
 OR (
bs:"[gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/" )
	(help)

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=1477674810.3607b7a4e355a2421321f2dfccc24f40f1d0d48e.ulm@gentoo \
    --to=ulm@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