Gentoo Archives: gentoo-commits

From: "Petteri Raty (betelgeuse)" <betelgeuse@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/devrel: new-dev-training.xml
Date: Tue, 11 Mar 2008 22:04:48
Message-Id: E1JZCaT-0007tX-Lu@stork.gentoo.org
1 betelgeuse 08/03/11 22:04:45
2
3 Modified: new-dev-training.xml
4 Log:
5 Remove references to digest files
6
7 Revision Changes Path
8 1.17 xml/htdocs/proj/en/devrel/new-dev-training.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/new-dev-training.xml?rev=1.17&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/new-dev-training.xml?rev=1.17&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/new-dev-training.xml?r1=1.16&r2=1.17
13
14 Index: new-dev-training.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/new-dev-training.xml,v
17 retrieving revision 1.16
18 retrieving revision 1.17
19 diff -u -r1.16 -r1.17
20 --- new-dev-training.xml 23 Jun 2007 18:48:03 -0000 1.16
21 +++ new-dev-training.xml 11 Mar 2008 22:04:45 -0000 1.17
22 @@ -16,8 +16,8 @@
23
24 <abstract>Instructions for new developers</abstract>
25
26 -<version>1.0.2</version>
27 -<date>24 April 2005</date>
28 +<version>1.1</version>
29 +<date>11 March 2007</date>
30
31 <chapter>
32 <title>Using CVS</title>
33 @@ -50,11 +50,6 @@
34 </pre>
35
36 <p>
37 -In order to make sure digests are correct, please put <c>cvs</c> in your
38 -<c>FEATURES</c> setting.
39 -</p>
40 -
41 -<p>
42 Finally, many people using CVS like to use compression (-z#). We ask that
43 developers who are not on dialup connections please use -z0 - with the contents
44 of our CVS repository and the load on our CVS server, you actually experience a
45 @@ -101,25 +96,27 @@
46 Say you're ready to add a brand new package, <c>foo</c>, in app-misc:
47 </p>
48
49 -<pre caption="add new package">
50 +<pre caption="add the ebuild">
51 # cd CVSROOT/app-misc <comment>(Replace CVSROOT with the location of your checked-out CVS tree.)</comment>
52 # cvs update <comment>(Always update before working in part of the tree!)</comment>
53 # mkdir foo
54 # cvs add foo <comment>(Here, we add the package directory foo to the CVS repository.)</comment>
55 # cd foo
56 # cp /path/to/foo-1.0.ebuild ./ <comment>(It's better to keep in-progress ebuilds in an overlay outside of your CVS tree.)</comment>
57 -# ebuild foo-1.0.ebuild digest <comment>(Make sure PORTDIR_OVERLAY is set to the CVS directory when creating digests.)</comment>
58 -# cvs add foo-1.0.ebuild files
59 -# cvs add files/digest-foo-1.0 <comment>(FEATURES=autoaddcvs will do this for you.)</comment>
60 -<comment>(Don't forget to create a ChangeLog - see the man page for echangelog.)</comment>
61 +# repoman manifest
62 +# cvs add foo-1.0.ebuild
63 </pre>
64
65 <p>
66 -Remember to also add a metadata.xml file with maintainer information. See the
67 +Create and add a metadata.xml file with maintainer information. See the
68 <uri link="/proj/en/devrel/handbook/handbook.xml?part=2&amp;chap=4">metadata guide</uri>
69 for more information.
70 </p>
71
72 +<pre caption="create ChangeLog">
73 +# echangelog "Initial commit. Ebuild written by me. Fixes bug #XXXXXX"
74 +</pre>
75 +
76 <p>
77 At this point, you're ready to commit (see the section on Commits below). But
78 what if you want to remove foo-1.0 when foo-1.1 is out?
79 @@ -128,8 +125,7 @@
80 <pre caption="commiting">
81 # cd CVSROOT/app-misc/foo
82 # cvs update
83 -# rm foo-1.0.ebuild files/digest-foo-1.0 <comment>(Files should be deleted first.)</comment>
84 -# cvs remove foo-1.0.ebuild files/digest-foo-1.0
85 +# cvs remove -f foo-1.0.ebuild
86 </pre>
87
88 <p>
89 @@ -153,7 +149,7 @@
90 <pre caption="repoman commit">
91 <comment>(Make sure there are no root-owned files present prior to running repoman.)</comment>
92 # repoman scan <comment>("scan" scans the current directory for QA issues. "full" is more complete.)</comment>
93 -# repoman commit <comment>("commit" does a scan, then commits, while also updating digests. Make sure to use a verbose and useful cvs changelog message.)</comment>
94 +# repoman commit <comment>("commit" does a scan, then commits, while also updating the manifest. Make sure to use a verbose and useful cvs changelog message.)</comment>
95 </pre>
96
97 </body>
98
99
100
101 --
102 gentoo-commits@l.g.o mailing list