From 34af93c76a54006d1512faed903586f0594b255d Mon Sep 17 00:00:00 2001 From: Darren Salt Date: Tue, 3 Apr 2007 18:33:44 +0100 Subject: Add appropriate Mercurial references and links. --- doc/faq/faq.sgml | 56 +++++++++++++++++++++++++++++------------- doc/hackersguide/overview.sgml | 2 +- 2 files changed, 40 insertions(+), 18 deletions(-) (limited to 'doc') diff --git a/doc/faq/faq.sgml b/doc/faq/faq.sgml index 51493089d..76cf5cb12 100644 --- a/doc/faq/faq.sgml +++ b/doc/faq/faq.sgml @@ -104,7 +104,7 @@ Other modules in CVS are: xine-plugin a mozilla browser plugin for streaming media playback using xine, - xine-www the + xine_www the xine project website sources. @@ -113,23 +113,45 @@ Where and how do I get the latest development version? Be advised that end-users should stick to the official xine releases. - CVS is only intended for developers and for others who know why they use it. - - - To check out xine-modules from CVS, first do this: -    cvs -d :pserver:anonymous@xine.cvs.sourceforge.net:/cvsroot/xine login - The password is empty, just press Enter. - - - Then, to check out individual modules (e.g. xine-lib or xine-ui): -    cvs -d :pserver:anonymous@xine.cvs.sourceforge.net:/cvsroot/xine co <modulename> - - - gxine's primary repository is at http://zap.tartarus.org/~ds/hg/gxine/. - Its CVS module is updated from this from time to time. - To check out the source: -    hg clone http://zap.tartarus.org/~ds/hg/gxine/ gxine + The CVS and Mercurial repositories are only intended for developers and for others who know why they use it. + + Checking out xine modules from Mercurial + + The repositories are listed at http://hg.debian.org/hg/; + however, this is a list of all repositories which are kept there, not just the + xine project's (which are the ones which begin with xine-lib/). To check one out: +    hg clone http://hg.debian.org/hg/repository local_copy + e.g. +    hg clone http://hg.debian.org/hg/xine-lib/xine-lib xine-lib + + + Currently, only xine-lib and gxine are present here. + + + If you have patches for a module which is maintained using mercurial, + you can make them available as diffs - use hg + export for this - or via HTTP by using hg + serve. In the latter case, you'll need to post a URL from + which a developer can pull the changes. We prefer these methods since + we get proper attribution this way. + + + + Checking out xine modules from CVS + + To check out xine modules from CVS, first do this: +    cvs -d :pserver:anonymous@xine.cvs.sourceforge.net:/cvsroot/xine login + The password is empty, just press Enter. + + + Then, to check out individual modules (e.g. xine-lib or xine-ui): +    cvs -d :pserver:anonymous@xine.cvs.sourceforge.net:/cvsroot/xine co <modulename> + + + If you want xine-lib or gxine, you should use Mercurial instead. + + diff --git a/doc/hackersguide/overview.sgml b/doc/hackersguide/overview.sgml index 0add48ade..d405ac18c 100644 --- a/doc/hackersguide/overview.sgml +++ b/doc/hackersguide/overview.sgml @@ -14,7 +14,7 @@ Everything below such a directory is up to this project. When modifying code there, be sure to send the patches on. If some xine specific adaptation of the code is absolutely necessary, a patch containing - the changes should be stored in CVS to not loose the changes the + the changes should be stored in Mercurial to not lose the changes the next time we sync with the external project. -- cgit v1.2.3