[gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/video: xine.xml

[Diego Petteno (flameeyes)]

flameeyes    07/12/30 13:42:40

  Modified:             xine.xml
  Log:
  Long awaited update: fixes information about snapshots (xine-lib is no
  more in CVS), notes the preference for hg exports for patches, links
  to the new xine bug tracker for patch and bugs submission, removes
  outdated information about X libraries, add information about
  Kaffeine's xcb USE flag, update repository information for gxine,
  removes the obsolete warning about xine-ui not seeing releases, don't
  suggest sending me patches for xine-ui (use the tracker instead),
  remove now useless information about musepack and samba USE flags,
  remove now obsolete refereces to the asf USE flag, document the
  previously unknown reasons why external dvdnav can't be used, and make
  it clear I don't maintain the ebuild first-hand anymore.

Revision  Changes    Path
1.28                 xml/htdocs/proj/en/desktop/video/xine.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/video/xine.xml?rev=1.28&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/video/xine.xml?rev=1.28&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/video/xine.xml?r1=1.27&r2=1.28

Index: xine.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/video/xine.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- xine.xml	30 Jan 2007 18:40:45 -0000	1.27
+++ xine.xml	30 Dec 2007 13:42:40 -0000	1.28
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/video/xine.xml,v 1.27 2007/01/30 18:40:45 flameeyes Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/video/xine.xml,v 1.28 2007/12/30 13:42:40 flameeyes Exp $ -->
 
 <guide link="/proj/en/desktop/video/xine.xml" lang="en">
 <title>xine-lib and related</title>
@@ -18,8 +18,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.21</version>
-<date>2007-01-30</date>
+<version>1.22</version>
+<date>2007-12-30</date>
 
 <chapter> <!-- xine-lib -->
 <title>xine-lib</title>
@@ -31,7 +31,7 @@
 
 <note>
 This guide was last updated for <c>xine-lib</c> version
-1.1.4
+1.1.8
 </note>
 
 <p>
@@ -80,7 +80,7 @@
 </p>
 
 <p>
-Since version 1.1.2 the patchset is heavily reduced, also because the current
+Since version 1.1.2 the patchset is heavily reduced, also because the former
 maintainer (<mail link="flameeyes@g.o">Diego Pettenò</mail>) is now
 contributing directly to
 <uri link="http://sourceforge.net/projects/xine">xine project</uri>. For this
@@ -95,11 +95,20 @@
 
 <p>
 If a patch that is not Gentoo-specific is being added to the ebuild, is usually
-suggested to send it to <path>xine-devel</path> mailing list on
-<uri link="http://sourceforge.net/projects/xine/">xine project space</uri> to
-be applied upstream.
+suggested to send it upstream through <uri
+link="http://bugs.xine-project.org/">their tracker</uri>, to be applied
+upstream. Similarly bugs that are not Gentoo specific are to be reported there
+so that they can be fixed directly by upstream. Backporting patches is an option
+once upstream fixed the issue.
 </p>
 
+<note>
+The preferred method to receive patches by the xine project is to send them as
+Mercurial exports: commit them on a local clone of the repository, and then use
+hg export to prepare the patch to send. This way the original author of the
+patch will be listed in the log.
+</note>
+
 <p>
 As <c>xine-lib</c> uses a number of libraries that are synced from time to time
 with its source tree, the patches that changes files imported from other
@@ -151,16 +160,16 @@
 <note>
 As also <path>libmad</path> is used external or not used at all, <c>xine-lib</c>
 might not be always able to decode mp3 audio without it. Since version
-1.1.2_pre20060328-r1 this doesn't lead to crashes anymore. Since version
+1.1.2_pre20060328-r1 this doesn't lead to crashes any longer. Since version
 1.1.3_pre20060929, even with mad useflag disabled MP3 files can be decoded
 through FFmpeg (albeit with some problems).
 </note>
 
 <p>
-An exception to the above rules applies to <c>libdvdnav</c>. For unknown reasons
-using the external library a lot of DVDs seems not to work reliably on xine
-(while they works fine on vlc using the same external library), and also seeking
-capabilities are lost, so the internal library is always used.
+An exception to the above rules applies to <c>libdvdnav</c>. The internal
+version in xine-lib is a CVS snapshot of the copy developed by the Linux DVD
+project, and thus works better than the last released copy. xine-lib 1.1 is not
+yet ready to use the new version developed by MPlayer project.
 </p>
 
 <p>
@@ -174,27 +183,17 @@
 </p>
 
 <p>
-The current ebuilds have to do some tricks to get the path for X libraries, such
-as libXv and libXvMC; the reason of this is that the default configure script
-does not seem to take the right libraries when looking for them in the usual
-places, and we need to pass them the right path. As their path depends vastly
-on the version of X11 installed in the system (that might be XFree or Xorg), the
-<c>get_x11_dir</c> function can be used to find them.
-</p>
-
-<p>
-In particular there's the problem that using three different XvMC libraries is
-a complex way to handle <b>xvmc</b> flag. There should be support for XvMCW
-library (that allows to configure at runtime which XvMC backend to use), but
-that requires a newer version of <c>xorg-x11</c>, the experimental 6.8.99 branch
-or the modular version.
+Older ebuilds had to do some tricks to get the path for X libraries such as
+libXv and libXvMC, as the default configure script didn't take the right
+libraries when looking for them in the usual places. This is now solved as the
+ebuilds depend on modular XOrg, and upstream configure now uses pkg-config for
+libraries discovery.
 </p>
 
 <p>
-All the above problems with <b>xvmc</b> useflag and the X libraries are solved
-with version 1.1.3_pre20060929 and later, as the forced dependency over Xorg 7
-allows to know where all the libraries are, and XvMCW presence allows to remove
-the need to select at buildtime the library to use for XvMC support.
+There also was a problem using three different XvMC libraries. Since version
+1.1.3_pre20060929, the <b>xvmc</b> USE flag uses the XvMCW wrapper library
+rather than choosing at build time one of the three libraries.
 </p>
 
 </body>
@@ -236,35 +235,13 @@
 </p>
 
 <p>
-The first note is about <b>win32codecs</b> useflag. This is used to enable
-the support for the binary win32 codecs that are emulated using a subset of
-Wine functions. This flag does not enable the ASF demuxer, so if you want to
-play WMV files you also need to enable the <b>asf</b> useflag. This flag is
-also needed to be able to play WMA files with <c>ffmpeg</c>. Since
-version 1.1.3 onward, as xine-lib supports decoding of WMV3 files
-through <c>ffmpeg</c>, the <b>asf</b> useflag is removed and it's
-always enabled, so it's then unneeded.
+The first note is about <b>win32codecs</b> useflag. This is used to enable the
+support for the binary win32 codecs that are emulated using a subset of Wine
+functions. Since version 1.1.3 onward, as xine-lib supports decoding of WMV9
+files through <c>ffmpeg</c>. The ASF demuxer is now forced enabled.
 </p>
 
 <p>
-Another flag having a special treatament is <b>xvmc</b>, that conditions the
-usage of three <c>VIDEO_CARDS</c> values that might be enabled directly as
-useflags or by setting the <c>VIDEO_CARDS</c> variable: <b>nvidia</b>,
-<b>i810</b> and <b>via</b>. The single <b>xvmc</b> alone will link
-<path>libXvMCW</path> if present, a wrapper library that allows to choose which
-other low-level library to use, while setting one of the other useflags will
-enable the correspondant driver. If more than one driver is enabled, the ebuild
-will behave as if none were enabled, thus using <path>libXvMCW</path> if present
-or disabling xvmc in the contrary.
-</p>
-
-<warn>
-As stated previously, since version 1.1.3_pre20060929 the above behaviour with
-<b>xvmc</b> and <c>VIDEO_CARDS</c> variable is now dropped, and libXvMCW is
-always used.
-</warn>
-
-<p>
 A note about the <b>debug</b> useflag is probably good; this useflag was added
 after request in
 <uri link="http://bugs.gentoo.org/show_bug.cgi?id=112980">bug #112980</uri>, and
@@ -287,24 +264,6 @@
 without this flag enabled.
 </p>
 
-<p>
-Since 1.1.4 pre-releases, a new <b>musepack</b> useflag appeared, that
-controls whether the musepack decoder plugin will be built or
-not. While before this was not controllable, and an internal copy of
-libmusepack was also used, since that version onward, the ebuild will
-force use of external libmpcdec library (new name of libmusepack
-library).
-</p>
-
-<p>
-The <b>samba</b> useflag, present in versions before 1.1.4, is now
-gone, and is now present only for 1.1.4 version onward. The reason for
-this change is that the smb input plugin was causing xine to crash,
-because a function was set to NULL and called without checking its
-value; this bug was resolved for 1.1.4 release, so the <b>samba</b>
-useflag was added back in it.
-</p>
-
 </body>
 </section>
 
@@ -341,23 +300,27 @@
 </section>
 
 <section> <!-- CVS Snapshot -->
-<title>CVS Snapshots</title>
+<title>Live Development Snapshots</title>
 
 <body>
 
 <p>
 Missing an updated release after 1.1.1, and this having quite a few of problems
 (counting in also a security issue), it happened that a pre-1.1.2 snapshot was
-made and also marked stable. In case there will be need for more CVS snapshots,
+made and also marked stable. In case there will be need for more snapshots,
 these are the basic instructions needed to generate one.
 </p>
 
 <p>
-The first thig is to get a CVS checkout of xine-lib sources, and making sure it
-is complete and not with a lot of FIXME in the log. After that you can use the
-simple command <c>make dist</c> to build a tarball to use for the ebuild. Make
-sure you try a <c>make distcheck</c> to ensure that everything is present,
-and run a few compile tests as well as runtime tests so that it works.
+The first thig is to get a Mercurial checkout of xine-lib sources from the
+proper branch. At the moment xine-lib is developed using Mercurial at <uri
+link="http://hg.debian.org/">Alioth</uri>, and the branch you're interested to
+is most likely the 1.1 branch <uri
+link="http://hg.debian.org/hg/xine-lib/xine-lib">http://hg.debian.org/hg/xine-lib/xine-lib</uri>.
+Make sure it is complete and not with a lot of FIXME in the log. After that you
+can use the simple command <c>make dist</c> to build a tarball to use for the
+ebuild. Make sure you try a <c>make distcheck</c> to ensure that everything is
+present, and run a few compile tests as well as runtime tests so that it works.
 </p>
 
 <p>
@@ -391,9 +354,9 @@
 </p>
 
 <p>
-Its handling is much simpler than <c>xine-lib</c>'s, the patches can still be
-sent upstream to <path>xine-devel</path> mailing list (or through Diego), and
-then dropped when the new releases are done.
+Its handling is much simpler than <c>xine-lib</c>'s, patches and bugs can still
+be sent upstream through <uri link="http://bugs.xine-project.org/">xine's
+tracker</uri>, and then dropped when the new releases are done.
 </p>
 
 <p>
@@ -404,20 +367,12 @@
 </p>
 
 <p>
-Missing (still) a 0.99.5 release, and having the previous one security issues,
-there's currently in the tree also a snapshot version that fixes a lot of
-stability issues, as well as a few security problems. Unfortunately
-this version, as of 30 January 2007 is also crashing when
-double-clicking the video window to go full screen. The bug is not
-solved in CVS yet.
+Missing a 0.99.5 release, and having the previous one security issues, there's
+currently in the tree also a snapshot version that fixes a lot of stability
+issues, as well as a few security problems. The new 0.99.5 version should solve
+all the previous issues.
 </p>
 
-<warn>
-If possible, please consider using another frontend for everything
-else but debugging, as its current maintainership status makes
-improbable a new release soon.
-</warn>
-
 </body>
 
 </section>
@@ -430,18 +385,16 @@
 <c>media-video/gxine</c> is a frontend based on GTK2 toolkit, it has fewer
 optional dependencies than <c>xine-ui</c> so it's usually simpler to manage.
 Although it had a few security vulnerabilities in the past, the new code should
-be safer. Patches to this can be sent to <path>xine-devel</path> mailing list as
-usual or to the upstream maintainer,
-<mail link="linux@××××××××××××××××××××××××.uk">Darren Salt</mail>.
+be safer. Patches to this can be sent to <uri
+link="http://bugs.xine-project.org/">xine's tracker</uri> as usual or to the
+upstream maintainer, <mail link="linux@××××××××××××××××××××××××.uk">Darren
+Salt</mail>. As per xine-lib, the patches are welcome as Mercurial commits exports.
 </p>
 
 <p>
-Unlike the rest of xine project software, gxine is not developed on a
-SourceForge.net CVS repository, but is instead managed as a Mercurial
-repository at <uri
-link="http://zap.tartarus.org/~ds/hg/gxine/">http://zap.tartarus.org/~ds/hg/gxine/</uri>,
-so the eventual patches can be sent upstream by exporting a Mercurial
-tree where they are applied.
+Like xine-lib, gxine is developed in a Mercurial repository at Alioth, you
+probably want to get the branch <uri
+link="http://hg.debian.org/hg/xine-lib/gxine">http://hg.debian.org/hg/xine-lib/gxine</uri>.
 </p>
 
 <p>
@@ -469,6 +422,15 @@
 to remember is that it requires a newer <c>xorg-x11</c> as there were troubles
 with old versions and with <c>xfree</c>.
 </p>
+
+<p>
+Kaffeine can use XCB library for xine video output, through the <b>xcb</b> USE
+flag, which requires <b>xcb</b> USE flag to be enabled in
+<c>media-libs/xine-lib</c> too. Upstream wants soon to make this a default
+non-switchable behaviour as without XCB, Kaffeine's embedding through KPart
+will make GwenView, Konqueror and other software crash at unload.
+</p>
+
 </body>
 </section>
 



-- 
gentoo-commits@g.o mailing list