Gentoo Archives: gentoo-commits

From: Markos Chandras <hwoarang@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/src_prepare/epatch/
Date: Sat, 28 Sep 2013 09:32:56
Message-Id: 1380360621.7fae06684e630b635562d10f603cb46d28902bc0.hwoarang@gentoo
1 commit: 7fae06684e630b635562d10f603cb46d28902bc0
2 Author: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
3 AuthorDate: Sat Sep 28 09:30:21 2013 +0000
4 Commit: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
5 CommitDate: Sat Sep 28 09:30:21 2013 +0000
6 URL: http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=7fae0668
7
8 epatch: Reword "larger patches"
9
10 Make it mention the devspace instead of mirrors
11
12 Bug 483292
13
14 ---
15 ebuild-writing/functions/src_prepare/epatch/text.xml | 2 +-
16 1 file changed, 1 insertion(+), 1 deletion(-)
17
18 diff --git a/ebuild-writing/functions/src_prepare/epatch/text.xml b/ebuild-writing/functions/src_prepare/epatch/text.xml
19 index a88ecaf..1322a5e 100644
20 --- a/ebuild-writing/functions/src_prepare/epatch/text.xml
21 +++ b/ebuild-writing/functions/src_prepare/epatch/text.xml
22 @@ -37,7 +37,7 @@ src_unpack() {
23 </codesample>
24
25 <p>
26 -For larger patches, using <c>mirror://gentoo/</c> rather
27 +For larger patches, using <uri link="::general-concepts/mirrors/#suitable-download-hosts">your devspace</uri> rather
28 than <c>files/</c> is more appropriate. In these situations, it is
29 usually best to <c>bzip2</c> the patch in question (as opposed to
30 <c>files/</c> patches, which must not be compressed). For example,