[packman] Fwd: commit libavutil for openSUSE:Factory

[Dominique Leuenberger a.k.a DimStar]

Hi everybody!

Small topic I would like to raise awareness for (in best case it's  
only to have it documented):

----- Forwarded message from root at suse.de -----
    Date: Fri, 15 Jun 2012 16:31:34 +0200
    From: root at suse.de
Subject: commit libavutil for openSUSE:Factory
      To: opensuse-commit at opensuse.org

Hello community,

here is the log from the commit of package libavutil for  
openSUSE:Factory checked in at 2012-06-15 15:41:42
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libavutil (Old)
  and      /work/SRC/openSUSE:Factory/.libavutil.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libavutil", Maintainer is ""

Changes:
--------
--- /work/SRC/openSUSE:Factory/libavutil/libavutil.changes	2012-06-13  
13:31:48.000000000 +0200
+++  
/work/SRC/openSUSE:Factory/.libavutil.new/libavutil.changes	2012-06-15  
16:31:33.000000000 +0200
@@ -1,0 +2,5 @@
+Fri Jun 15 04:03:15 UTC 2012 - factory-maintainer at kulow.org
+
+- add -32bit library for xine to use
+
+-------------------------------------------------------------------

So, that means we now do have libavutil in Factory?

Has this be well planned and the side effects are well known?  
Especially be aware that PackMan and VLC Repo both carry this library  
as part of the ffmpeg builds. frankly, I'm *scared* of side effects  
being introduced here:
PM / VLC will likely move to 'more recent' (or just 'different')  
versions of ffmpeg in no time. having libavutil now part of Factory  
will make it VERY likely to cause issues on all kind of applications  
coming from those repos; an updated ffmpeg in any of those repos will  
need to be SURE it gets libavutil51 ALSO from that repo.

Was this addition a real NEED or just a 'nice to have without gain'? I  
mean: xine-lib STAYS crippled, there is nothing we can do. Adding  
libavutil does not change that. A user wanting full 'fun' still needs  
to replace parts of the dist...

'Adding' new software now might start to replace libs as well (VLC  
Repo for example used to have the rule to NOT carry libs that are part  
of the distribution, in order to never have to replace them... )

Or am I just seeing issues where there are none and all of the packman  
/ vlc issues will not happen? Then I'm happy to hear that this will  
not introduce more trouble.

Best regards,
Dominique