Contents of /xml/htdocs/proj/en/overlays/devguide.xml

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.10 - (hide annotations) (download) (as text)
Sun Oct 12 09:23:30 2008 UTC (10 years, 5 months ago) by robbat2
Branch: MAIN
Changes since 1.9: +11 -3 lines
File MIME type: application/xml
Flip instructions to note HTTPS for all commit actions.

1 stuart 1.1 <?xml version="1.0" encoding="UTF-8"?>
2     <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4     <guide link="/proj/en/overlays/devguide.xml">
5     <title>Gentoo Overlays: Developers' Guide</title>
7     <author title="Author">
8     <mail link="stuart@gentoo.org">Stuart Herbert</mail>
9     </author>
11     <abstract>This guide helps developers understand how to use the Gentoo
12     Overlays service.</abstract>
14     <license/>
16     <version>1.0</version>
17     <date>2006-07-29</date>
19     <chapter>
20     <title>Introduction</title>
22     <section>
23     <title>Audience</title>
24     <body>
25     <p>This document has been written for Gentoo developers and Gentoo staff members. If you are a Gentoo user, or you just want to start downloading and using overlays, please see <uri link="/proj/en/overlays/userguide.xml">the Gentoo Overlays User Guide</uri> instead.</p>
26     </body>
27     </section>
29     <section>
30     <title>What is overlays.gentoo.org?</title>
31     <body>
32     <p><uri link="http://overlays.gentoo.org">overlays.gentoo.org</uri> provides social workspaces to allow Gentoo projects, developers and users to collaborate together on tomorrow's Gentoo packages. We do this by hosting overlays for Gentoo projects, and overlays for Gentoo developers.</p>
33     </body>
34     </section>
36     <section>
37     <title>Who Can Use overlays.gentoo.org?</title>
38     <body>
39     <p>Any Gentoo project, or Gentoo developer, can have their own overlay hosted on overlays.gentoo.org, with the RSS feed from the changelog included on <uri link="http://overlays.gentoo.org">the overlays.gentoo.org homepage</uri>.</p>
41     <p>Any Gentoo staff member or user (ie, anyone who doesn't have write access to
42     the main Portage package tree) can download and use the contents of any hosted
43     overlay. If you choose, you can also give users write access to your
44     overlay.</p>
45     </body>
46     </section>
48     <section>
49     <title>What Does overlays.gentoo.org Give Me?</title>
50     <body>
51     <p>The overlays.gentoo.org service currently provides:</p>
52     <ul>
53     <li><uri link="http://trac.edgewall.com">Trac</uri> (a wiki w/ integrated subversion browser), for quickly creating and maintaining documentation about your overlay</li>
54     <li><uri link="http://subversion.tigris.org">Subversion</uri> - a centralised version control system (distributed version control systems will be supported in future)</li>
55     <li>Publishing the changelog for your overlay on <uri link="http://overlays.gentoo.org/">the o.g.o homepage</uri>, so that everyone who's interested can see what's going on</li>
56     </ul>
58     <p>... all hosted on secure, backed-up Gentoo infrastructure, administered by
59     <uri link="/proj/en/infrastructure">the Gentoo Infrastructure team</uri> (hardware / base OS) and <uri link="/proj/en/overlays">the Gentoo Overlays team</uri>
60     (wiki / VCS / ACLs).</p>
62     <p>Each overlay has separate authentication lists for Trac and for Subversion.
63     It's no problem at all to give someone write access to just Trac (e.g. for
64     writing documentation) without giving them write access to Subversion.</p>
65     </body>
66     </section>
68     <section>
69     <title>Why Should We Use overlays.gentoo.org?</title>
70     <body>
71     <p>You don't have to. You don't have to have an overlay at all, and if you do
72     have one, you are absolutely free to host your own overlay somewhere else.
73     You don't have to host an overlay on o.g.o for it to be considered
74     "official".</p>
76     <p>The advantage of using overlays.gentoo.org is that we already have everything
77     setup for you. You don't need to admin your own server, or worry about
78     software upgrades. We take care of all of that for you.</p>
79     </body>
80     </section>
82     <section>
83     <title>When Should We Not Use overlays.gentoo.org?</title>
84     <body>
85     <p>The purpose of o.g.o is to help bridge the gap between developers and users.
86     Gentoo is a community-based distribution, and we believe that our users are
87     just as important a part of that community as developers are.</p>
89     <p>All of the overlays hosted on o.g.o are there for all users to download and
90     use. It's for users to make their own decision about what software they
91     install on their computers - and that includes choosing to use your overlay.
92     Some users will make bad decisions, and end up breaking their computer. They
93     may even end up blaming Gentoo as a result. That's okay; these people
94     probably go around blaming everyone but themselves for their own
95     mistakes anyway, and there's probably nothing you can do to change that.
96     But that still doesn't give any of us the right to choose for them.</p>
98     <p>Users are free (in fact, they are encouraged) to provide constructive
99     feedback about anything to do with Gentoo - including all of the overlays
100     hosted on o.g.o. That feedback can come via bugs.g.o, via email to your
101     project team or directly to you, via the forums, or via IRC. We're not
102     talking about genuinely abusive users; we have no time for those, and no-one
103     expects you to have any time for them either.</p>
105     <warn>If you're not happy with users using your overlay, and / or if you don't want
106     users bothering you about your overlay, then don't use o.g.o to host your
107     overlay.</warn>
109     <p>The other thing we need to say is that o.g.o is for hosting overlays. You
110     can't use it to be $UPSTREAM for your packages. If that's the kind of hosting
111     you need, you can use services such as <uri link="http://www.sourceforge.net/">SourceForge.net</uri>, <uri link="http://www.berlios.de">Berlios</uri>, or
112     Patrick's <uri link="http://www.gentooexperimental.org">GentooExperimental.org</uri>.</p>
113     </body>
114     </section>
115     </chapter>
117     <chapter>
118     <title>Requesting An Overlay</title>
120     <section>
121     <title>Introduction</title>
122     <body>
123     <p>There are two types of overlay - "project" overlays, and "developer"
124     overlays. The only difference between them is responsibility and
125     accountability.</p>
127     <impo>Before requesting an overlay, please make sure that you have read our <uri link="/proj/en/overlays/policy.xml">Policy Document</uri>. It clearly sets out what's allowed and what is not, and what your responsibilities will be.</impo>
128     </body>
129     </section>
131     <section>
132     <title>Project Overlays</title>
133     <body>
134     <p>"Project" overlays are overlays for official Gentoo projects. A good
135     example is <uri link="http://overlays.gentoo.org/proj/php">the PHP Overlay</uri>.</p>
137     <p>An official Gentoo project is a project that has a project page on
138     www.gentoo.org, and that has an elected lead. (This definition comes from <uri link="http://www.gentoo.org/proj/en/glep/glep-0039.html">the
139     metastructure document</uri>, which is Gentoo's governing document). The project
140     lead(s) are responsible for the project overlay, including its contents, and
141     any problems it causes other Gentoo projects and developers.</p>
143     <p>To request a project overlay, the project's lead just needs to pop into
144     #gentoo-overlays on IRC and ask for an overlay to be created. Or, if he/she
145     prefers, drop an email to overlays@gentoo.org. We'll take care of the rest,
146     including granting write access to all the members of your project (as listed
147     on your project page).</p>
149     <p>We will:</p>
150     <ul>
151     <li>create your overlay (trac site + svn)</li>
152     <li>add your overlay's RSS feed to the o.g.o homepage</li>
153     <li>create an o.g.o account for you if you don't already have one</li>
154     <li>give you write access to your overlay's Trac wiki and Subversion
155     repository</li>
156     <li>give write access to all project members who already have an o.g.o
157     account</li>
158     <li>contact all of the other project members, and sort out their access</li>
159     </ul>
160     </body>
161     </section>
163     <section>
164     <title>Developer Overlays</title>
165     <body>
167     <p>"Developer" overlays are overlays owned by individual Gentoo developers. One
168     example is <uri link="http://overlays.gentoo.org/dev/tcort">tcort's overlay</uri>.</p>
170     <p>If you have an @gentoo.org email address, and you've passed the ebuild quiz,
171     then you can have your own developer overlay on o.g.o.</p>
173     <p>To request a developer overlay, just pop into #gentoo-overlays on IRC and ask
174     for an overlay to be created for you. Or, if you prefer, drop an email to
175     overlays@gentoo.org.</p>
177     <p>We will:</p>
178     <ul>
179     <li>create your overlay (trac site + svn)</li>
180     <li>add your overlay's RSS feed to the o.g.o homepage</li>
181     <li>create an o.g.o account for you if you don't have one already</li>
182     <li>give you write access to your overlay's Trac wiki and Subversion
183     repository</li>
184     </ul>
185     </body>
186     </section>
188     <section>
189     <title>A Word About Accounts</title>
190     <body>
191     <p>Because o.g.o is designed to support a blend of both Gentoo developers and
192     Gentoo users, we don't create 'real' system-level accounts on the o.g.o host.
193     All access is currently through Apache, and is managed by Apache htpasswd and
194     htgroup files.</p>
196     <impo>You do *not* have SSH access to o.g.o.</impo>
197     </body>
198     </section>
199     </chapter>
201     <chapter>
202     <title>Working With Your Overlay</title>
204     <section>
205     <title>Introduction</title>
206     <body>
207     <p>You can access your overlay as soon as it has been created. Project and
208     developer overlays have different URLs, so that everyone can tell one from the
209     other, but otherwise they are identical in every way.</p>
211     <p>There are *no* read restrictions on overlays or wikis. Everyone has full
212     read access to all overlays and wikis. If you need a 'secret' overlay of some
213     kind, then o.g.o is not for you.</p>
214     </body>
215     </section>
217     <section>
218     <title>Accessing Project Overlays</title>
219     <body>
220     <p>If your project overlay is called 'foo', your Trac wiki site will be
221     here: http://overlays.gentoo.org/proj/foo/</p>
223     <p>To checkout your Subversion repository, use:</p>
224 robbat2 1.10 <pre caption="Checkout your project overlay">svn co https://overlays.gentoo.org/svn/proj/foo/</pre>
226     <p>While you may perform read-only actions via unsecure HTTP, you must perform
227     all commits via HTTPS. If you need to switch between modes, use:</p>
228     <pre caption="Switching your project overlay from HTTP to HTTPS">svn sw --relocate http://overlays.gentoo.org/svn/proj/foo/ https://overlays.gentoo.org/svn/proj/foo/</pre>
229 stuart 1.1
230     <p>We maintain <uri link="http://overlays.gentoo.org/proj/">a full list of project overlays hosted on overlays.gentoo.org</uri>.</p>
231     </body>
232     </section>
234     <section>
235     <title>Accessing Developer Overlays</title>
236     <body>
237     <p>If your Gentoo email address is 'foo@gentoo.org', your Trac wiki site will be
238     here: http://overlays.gentoo.org/dev/foo/</p>
240     <p>To checkout your Subversion repository, use:</p>
241 robbat2 1.10 <pre caption="Checkout your developer overlay">svn co https://overlays.gentoo.org/svn/dev/foo/</pre>
243     <p>While you may perform read-only actions via unsecure HTTP, you must perform
244     all commits via HTTPS. If you need to switch between modes, use:</p>
245     <pre caption="Switching your developer overlay from HTTP to HTTPS">svn sw --relocate http://overlays.gentoo.org/svn/dev/foo/ https://overlays.gentoo.org/svn/dev/foo/</pre>
246 stuart 1.1
247     <p>We maintain <uri link="http://overlays.gentoo.org/dev/">a full list of developer overlays hosted on overlays.gentoo.org</uri>.</p>
248     </body>
249     </section>
251     <section>
252     <title>Getting Started With Trac</title>
253     <body>
254     <p>Your overlay comes with <uri link="http://trac.edgewall.com">Trac</uri>. Trac is a wiki, a subversion repository browser, and a bug tracking system that's
255     very popular with open source developers.</p>
257     <p>We have disabled the bug tracking system in Trac. Use <uri link="http://bugs.gentoo.org">Gentoo's bugzilla</uri> for bug tracking your overlay.</p>
259     <p>Your overlay's RSS feed - the one that is shown on <uri link="http://overlays.gentoo.org">the o.g.o homepage</uri> - comes from Trac's Timeline page.</p>
261     <p>We have installed several Trac plugins, which we hope will make your wiki even
262     more useful to you. If you come across any additional plugins that you'd like
263     to see installed, please let us know, and we'll take a look at them.</p>
265 stuart 1.2 <ul>
266     <li><e>LayOnTrac</e> - lists the packages from the overlay.</li>
267     <li><uri link="http://muness.textdriven.com/trac/wiki/tags/Setup">TracTags</uri> - displays a tag cloud</li>
268     <li><uri link="http://trac.edgewall.org/wiki/WebAdmin">TracWebAdmin</uri> - provides web-based admin panel for Trac</li>
269     </ul>
271     <p>We have installed several Trac macros, which we hope will make your wiki even more useful to you. If you come across any additional macros that you'd like to see installed, please let us know, and we'll take a look at them.</p>
273     <ul>
274     <li><uri link="http://trac-hacks.org/wiki/AddCommentMacro">AddComment</uri> - allows visitors to add comments to the bottom of your pages</li>
275     <li><uri link="http://trac-hacks.org/wiki/FootNoteMacro">FootNote</uri> - adds support for adding footnotes to a page</li>
276     <li><uri link="http://trac-hacks.org/wiki/TocMacro">TOC</uri> - adds support for publishing a Table of Contents on a page</li>
277     </ul>
279 stuart 1.1 </body>
280     </section>
282     <section>
283     <title>Getting Started With Subversion</title>
284     <body>
285     <p>Your overlay comes with <uri link="http://subversion.tigris.org">Subversion</uri>, a modern alternative to CVS. The advantages of Subversion over CVS include real versioning of directories, full changeset support, and it's much easier to do branching if you need to. The main disadvantage of Subversion is that it is slower than CVS, and that a local Subversion checkout requires more disk space.</p>
287 stuart 1.3 <p>If you have never used Subversion before, the <uri link="http://svnbook.red-bean.com/">online book</uri> is an excellent way to learn Subversion. You can buy it in dead-tree format too if you prefer.</p>
288 stuart 1.1
289 stuart 1.2 <p>Here are some basic commands to get you started.</p>
290 robbat2 1.10 <pre caption="Checking out your overlay">svn co https://overlays.gentoo.org/proj/php</pre>
291 stuart 1.2 <pre caption="Seeing which files need committing">svn status</pre>
292     <pre caption="Adding files to your overlay">svn add my.ebuild</pre>
293     <pre caption="Committing your changes">svn commit -m 'My changelog entry'</pre>
294 stuart 1.1
295     </body>
296     </section>
298     <section>
299     <title>Layman</title>
300     <body>
301     <p>We are telling users to use layman to download and manage your overlay.
302     layman is a utility written by <mail link="wrobel@gentoo.org">Gunnar Wrobel</mail> which makes it very easy for users to work with overlays.</p>
304     <p>To get started with using layman, see <uri link="http://www.gentoo.org/news/en/gwn/20060522-newsletter.xml">Gentoo Weekly News for 22nd May</uri>, <uri link="http://gentoo-wiki.com/TIP_Overlays#layman">this article on Gentoo-Wiki.com</uri>, or the man page that comes with layman.</p>
305     </body>
306     </section>
308     <section>
309     <title>Auto-Sync From Portage</title>
310     <body>
311     <p>Your packages in the Portage tree are always at risk of being changed without
312     you knowing about it in advance. Arch teams need to be able to keyword
313     packages (and fix arch-specific brokenness), the QA team fix perceived
314     standards violations, and occaisionally developers will edit packages that
315     they shouldn't.</p>
317     <p>You need to make sure that the changes made in Portage aren't lost the next
318     time you copy your packages from your overlay back into Portage.</p>
320     <p>The PHP team have solved this problem by automatically copying their packages
321     from Portage back into a 'portage' branch of their overlay every night. They
322 chtekk 1.9 can then use Subversion (or Trac's timeline) to see what has changed every day.</p>
323 stuart 1.1
324     </body>
325     </section>
326     </chapter>
328     <chapter>
329 genstef 1.8 <title>Using git on overlays</title>
331     <section>
332     <title>Setting up git for committing with webdav</title>
333     <body>
334     <pre caption="add to your ~/.netrc">
335     machine overlays.gentoo.org
336     login (your-username)
337     password (your-password)
338     </pre>
339     <p>Source: http://www.kernel.org/pub/software/scm/git/docs/howto/setup-git-server-over-http.txt</p>
340     </body>
341     </section>
342     <section>
343     <title>Initializing your overlay</title>
344     <body>
345     <p>Before uploading you need to locally create a git repository and add all items:</p>
346     <pre caption="go to your overlay">cd ~/my-overlay</pre>
347     <pre caption="create a new git repo">git init
348     git add .
349     git commit -m "populate overlay"</pre>
350     <p>Note that this commit was only locally, now we get the server into the game. Be sure to add the trailing /</p>
351     <pre caption="tell git the url">git-config remote.upload.url http://(your-username)@overlays.gentoo.org/git/(proj or dev)/(name)/</pre>
352     <pre caption="finally get it up there">git push upload master</pre>
353     <p>Source: http://www.kernel.org/pub/software/scm/git/docs/tutorial.html</p>
354     </body></section>
356     <section>
357     <title>Checking out the overlay with git</title>
358     <body>
359     <pre caption="clone it!">git clone http://overlays.gentoo.org/git/(proj or dev)/(name)/</pre>
360     </body>
361     </section>
362     </chapter>
364     <chapter>
365 stuart 1.1 <title>Giving Access To Your Overlay To Others</title>
367     <section>
368     <title>Introduction</title>
369     <body>
370     <p>One of the key features of o.g.o is that people who do not have write access
371     to the Gentoo Portage package tree can have write access to one or more
372     overlays. Several Gentoo projects have found that this is a great way to train
373     and evaluate potential Gentoo developers in a safe environment.</p>
375     <p>At the moment, only the Overlays team can update the access control lists for
376     overlays.gentoo.org. We will provide a web-based tool for managing the access
377     control lists at a later date. But, for now, if you need a change made,
378     please drop by #gentoo-overlays on IRC for assistance.</p>
379     </body>
380     </section>
382     <section>
383     <title>Project Overlays: Giving Write Access To Team Members</title>
384     <body>
385     <p>Any developer listed on a team's project page on www.g.o can have write
386     access to the team's overlay. The project lead can ask on their behalf, or
387     the developer can come and ask for access themselves.</p>
389     <p>If the developer doesn't have an o.g.o account yet, he/she will need to drop
390     by #gentoo-overlays so that we can create an account for them.</p>
391     </body>
392     </section>
394     <section>
395     <title>Project Overlays: Giving Write Access To Other Gentoo
396     Developers</title>
397     <body>
399     <p>Any Gentoo developer *not* listed on a team's project page on www.g.o can
400     have write access to the team's overlay. The request for write access must
401     come from a member of the team. It doesn't have to come from the project
402     lead.</p>
404     <p>If the developer doesn't have an o.g.o account yet, he/she will need to drop
405     by #gentoo-overlays so that we can create an account for them.</p>
406     </body>
407     </section>
409     <section>
410     <title>Project Overlays: Giving Write Access To Gentoo Users</title>
411     <body>
412     <p>Any Gentoo user can have write access to the team's overlay. The request for
413     write access must come from one of the project's leads. You can request that
414     we give the user write access to Trac, to Subversion, or to both. (We will
415     assume that the request is for write access to both, unless you say
416     otherwise).</p>
418     <p>We cannot accept these requests from anyone other than a project lead. If
419     your project only has the one lead, we recommend electing a second lead. If
420     your one and only lead is AWOL, consider electing a replacement :)</p>
422     <p>If the user doesn't have an o.g.o account yet, he/she will need to drop by
423     #gentoo-overlays so that we can create an account for them.</p>
424     </body>
425     </section>
427     <section>
428     <title>Developer Overlays: Giving Write Access To Gentoo Developers</title>
429     <body>
430     <p>Any Gentoo developer can have write access to your developer overlay. The
431     developer can ask us directly; we will not give access until we've checked
432     with you. You can also ask us to give write access to any named
433     developer.</p>
435     <p>If the developer doesn't have an o.g.o account yet, he/she will need to drop
436     by #gentoo-overlays so that we can create an account for them.</p>
437     </body>
438     </section>
440     <section>
441     <title>Developer Overlays: Giving Write Access To Gentoo Users</title>
442     <body>
443     <p>Any Gentoo user can have write access to your developer's overlay. The
444     request for write access must come from you. You can request that we give
445     the user write access just to Trac, just to Subversion, or to both. (We will
446     assume that the request is for write access to both unless you say
447     otherwise).</p>
449     <p>We cannot accept these requests from anyone else other than you. If you find
450     yourself giving access to a lot of other people, it might be that you should
451     consider setting up a new project, and transfering your work there
452     instead.</p>
454     <p>If the user doesn't have an o.g.o account yet, he/she will need to drop by
455     #gentoo-overlays so that we can create an account for them.</p>
456     </body>
457     </section>
458     </chapter>
460     <chapter>
461     <title>Accessing Someone Else's Overlay</title>
463     <section>
464     <title>Using An Overlay</title>
465     <body>
466     <p>Everyone has full read access to every overlay. We recommend that you
467     use</p>
468     <pre caption="Install layman">
469     emerge layman
470     echo 'source /usr/portage/local/layman/layman.conf' &gt;&gt; /etc/make.conf
471     </pre>
473 wrobel 1.6 <note>
474 wrobel 1.7 Layman will create "/usr/portage/local/layman/make.conf" once you add
475     your first overlay. But if you do not plan to install an overlay
476     immediately you should ensure that this file actually exists and
477     contains the empty variable "PORTDIR_OVERLAY". Otherwise portage will
478     complain. You can run "echo PORTDIR_OVERLAY=\"\" >
479     /usr/portage/local/layman/make.conf" in order to have the file created
480     correctly.
481 wrobel 1.6 </note>
483 stuart 1.1 <p>After that, to view the list of overlays, use</p>
485     <pre caption="List overlays that layman knows about">layman -L</pre>
487     <p>To install an overlay, use</p>
488     <pre caption="Install an overlay">layman -a &lt;overlay-name&gt;</pre>
490     <p>You can now install packages from the overlay.</p>
491     </body>
492     </section>
494     <section>
495     <title>Requesting Write Access</title>
496     <body>
497     <p>If you want write access to a project overlay, contact a member of the
498     project team, and ask them for access. If they approve your request, they
499     will arrange for you to have write access, by contacting the Overlays
500     team.</p>
502     <p>If you want write access to a developer's overlay, contact the developer
503     directly, and ask them for access. If they approve your request, they will
504     arrange for you to have write access, by contacting the Overlays team.</p>
505     </body>
506     </section>
507     </chapter>
509     <chapter>
510     <title>Frequently Asked Questions</title>
512     <section>
513     <title>o.g.o Administration</title>
514     <body>
516     <p>Q: How do I contact the o.g.o admin staff?</p>
517     <ul>
518     <li>A: You can pop into #gentoo-overlays on IRC, and talk to us there. The
519     current staff are mostly in European timezones.</li>
520     <li>A: You can send an email to overlays@gentoo.org. Someone will answer you as
521     soon as possible.</li>
522     <li>A: You can contact Stuart Herbert (the project leader) directly, via his
523     email address: stuart@gentoo.org.</li>
524     </ul>
526     <p>Q: Why can't I edit the access control list directly?</p>
527     <ul>
528     <li>A: The access control list currently lives in htpasswd / htgroup files used
529     by Apache. Only o.g.o admin staff have ssh access into the o.g.o box.</li>
530     </ul>
531     </body>
532     </section>
534     <section>
535     <title>Security</title>
536     <body>
537     <p>Q: Is my overlay available via https?</p>
538     <ul>
539 stuart 1.4 <li>A: Yes, it is.</li>
540 stuart 1.1 </ul>
541     </body>
542     </section>
544     <section>
545     <title>Multiple Overlays</title>
546     <body>
548     <p>Q: Can I have multiple overlays?</p>
549     <ul>
550     <li>A: Yes, in a fashion. Inside your overlay, you can create
551     sub-directories, and put separate package trees inside those sub-directories.
552     Please take a look at the PHP project overlay for an example.</li>
553     </ul>
554     </body>
555     </section>
557     <section>
558     <title>Importing Existing Overlays</title>
559     <body>
560     <p>Q: I already have an overlay, and I'd like to move it to o.g.o. How do I
561     go about doing that?</p>
562     <ul>
563     <li>A: Create a tarball of your subversion repository, and put it somewhere
564     where it can be downloaded via http. We'll download it and install it onto
565     o.g.o for you.</li>
566     </ul>
567     <note>Make sure you tar up your repository, and not a checkout!</note>
569     <p>Q: I have an overlay, but it doesn't use Subversion. How do I go about
570     moving it to o.g.o?</p>
571     <ul>
572     <li>A: Ask us to create a new, empty overlay for you. You can then use 'svn
573     import' to import your files into the new overlay. You'll lose your history,
574     but that can't be helped.</li>
575     <li>A: Search the Internet, and see if there is a tool to convert from your
576     existing version control software to Subversion. If there is, use that, and
577     then we can help you move it to o.g.o.</li>
578     <li>A: If your version control software is used by Trac, and it can be used
579     over HTTP, come and help us add
580     support for your version control software on o.g.o.</li>
581     </ul>
582     </body>
583     </section>
585     <section>
586     <title>"Official" Overlays</title>
587     <body>
588     <p>Q: When is an overlay considered "official"?</p>
589     <ul>
590     <li>A: An "official" overlay is an overlay managed by a Gentoo project (for
591     project overlays) or a Gentoo developer (for developer overlays).</li>
592     </ul>
594     <p>Q: Does an overlay have to be on o.g.o to be "official"?</p>
595     <ul>
596     <li>A: No.</li>
597     </ul>
598     </body>
599     </section>
600     </chapter>
601     </guide>

  ViewVC Help
Powered by ViewVC 1.1.20