summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-July/006403.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2011-July/006403.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-dev/2011-July/006403.html')
-rw-r--r--zarb-ml/mageia-dev/2011-July/006403.html224
1 files changed, 224 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-July/006403.html b/zarb-ml/mageia-dev/2011-July/006403.html
new file mode 100644
index 000000000..6d0af10a4
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-July/006403.html
@@ -0,0 +1,224 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] gstreamer packaging too split?
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20gstreamer%20packaging%20too%20split%3F&In-Reply-To=%3C4E1457CA.3010701%40colin.guthr.ie%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="006365.html">
+ <LINK REL="Next" HREF="006406.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] gstreamer packaging too split?</H1>
+ <B>Colin Guthrie</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20gstreamer%20packaging%20too%20split%3F&In-Reply-To=%3C4E1457CA.3010701%40colin.guthr.ie%3E"
+ TITLE="[Mageia-dev] gstreamer packaging too split?">mageia at colin.guthr.ie
+ </A><BR>
+ <I>Wed Jul 6 14:40:42 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="006365.html">[Mageia-dev] gstreamer packaging too split?
+</A></li>
+ <LI>Next message: <A HREF="006406.html">[Mageia-dev] gstreamer packaging too split?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6403">[ date ]</a>
+ <a href="thread.html#6403">[ thread ]</a>
+ <a href="subject.html#6403">[ subject ]</a>
+ <a href="author.html#6403">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>'Twas brillig, and Ahmad Samir at 05/07/11 10:50 did gyre and gimble:
+&gt;&gt;<i> I see packages like gstreamer0.10-soup installed as separate packages.
+</I>&gt;&gt;<i> Is there any real gain from this split? Other than pulling in other
+</I>&gt;&gt;<i> libraries etc, as it just causes potential problems for some packages
+</I>&gt;&gt;<i> that do not require it. e.g. totem and rhythmbox both reqire the -soup
+</I>&gt;&gt;<i> package but phonon-gstreamer does not (it should).
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> But really, should this library just be bundled into the main -good
+</I>&gt;&gt;<i> package?
+</I>&gt;<i>
+</I>&gt;<i> I agree about merging -soup, without it gst-based apps can't seem to
+</I>&gt;<i> play online streams, this is a basic functionality, I guess.
+</I>&gt;<i>
+</I>&gt;&gt;<i> Ditto for other &quot;overly split&quot; things, like the pulse plugin,
+</I>&gt;&gt;<i> and the neon plugin in -bad....
+</I>&gt;&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> I dunno about pulse, it would pull pulseaudio on users' systems (I
+</I>&gt;<i> know it's installed by default, but some do a minimal install and
+</I>&gt;<i> don't install pulse, even if the some of pulse libs are too dug deep
+</I>&gt;<i> down the whole stack :)).
+</I>
+Hmmm, gstreamer0.10-pulse requires &quot;pulseaudio &gt;= 0.9.7&quot;. Interesting.
+
+I'm not sure why (it could easily be installed on a system that does not
+have a PA daemon and operates as a thin client.
+
+Wonder if we should just drop that require and then the gst-pulse plugin
+only really requires libpulse which a *lot* of other things need anyway,
+and thus no additional stuff pulled in. WDYT?
+
+
+&gt;&gt;<i> Has anyone sad down and thought about it a bit recently (here or in Mdv?)
+</I>&gt;<i>
+</I>&gt;<i> (I have to admit, I didn't sit down and think about it before). Here goes:
+</I>&gt;<i>
+</I>&gt;<i> ===========================
+</I>&gt;<i> -good:
+</I>&gt;<i> $ urpmf --sourcerpm gstreamer0.10-plugins-good | awk -F: '{print $1}'
+</I>&gt;<i> gstreamer0.10-caca
+</I>&gt;<i> gstreamer0.10-raw1394
+</I>&gt;<i> gstreamer0.10-soup
+</I>&gt;<i> gstreamer0.10-plugins-good
+</I>&gt;<i> gstreamer0.10-dv
+</I>&gt;<i> gstreamer0.10-wavpack
+</I>&gt;<i> gstreamer0.10-pulse
+</I>&gt;<i> gstreamer0.10-jack
+</I>&gt;<i> gstreamer0.10-speex
+</I>&gt;<i> gstreamer0.10-aalib
+</I>&gt;<i> gstreamer0.10-flac
+</I>&gt;<i>
+</I>&gt;<i> I think these can be merged in addition to -soup:
+</I>&gt;<i> -flac, an open format, expected to work o-o-t-b, IMHO
+</I>&gt;<i> -jack, doesn't matter really, it won't pull any more requires as
+</I>&gt;<i> libjack.so.0 is deep in the stack anyway (just tested with urpme
+</I>&gt;<i> --test and it wanted to yank 174 packages).
+</I>&gt;<i>
+</I>&gt;<i> As for the rest I am not sure, e.g. I've never used -wavpack, so I
+</I>&gt;<i> think they can remain split.
+</I>
+Perhaps, but I'm just not convinced of the value of a split generally.
+Sure you could argue that pulling in an extra lib here and there can
+count for a lot of disk space, but then we end up with various problems
+for other packages (like the soup issue - although granted, one as
+obvious as that will likely not crop up with the more subtle extras -
+until some user plugs in their dv video camera...... :p)
+
+&gt;<i> =========================
+</I>&gt;<i> -ugly looks OK to me.
+</I>&gt;<i>
+</I>&gt;<i> $ urpmf --sourcerpm gstreamer0.10-plugins-ugly | awk -F: '{print $1}'
+</I>&gt;<i> gstreamer0.10-sid
+</I>&gt;<i> gstreamer0.10-twolame
+</I>&gt;<i> gstreamer0.10-a52dec
+</I>&gt;<i> gstreamer0.10-cdio
+</I>&gt;<i> gstreamer0.10-plugins-ugly
+</I>&gt;<i> gstreamer0.10-mpeg
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> Though merging -a52dec looks like a good idea given how widely used
+</I>&gt;<i> the AC-3 codec is.
+</I>&gt;<i>
+</I>&gt;<i> ==========================
+</I>&gt;<i> I left the &quot;bad&quot; for last, they look OK too, each sub-package
+</I>&gt;<i> pulls/requires a different lib (e.g. rtmp -&gt; librtmp.so.0), I guess
+</I>&gt;<i> that's a good splitting criteria; I've never used -neon so I'll take
+</I>&gt;<i> your word for it :)
+</I>&gt;<i> $ urpmf --sourcerpm gstreamer0.10-plugins-bad | awk -F: '{print $1}' |
+</I>&gt;<i> grep -v lib
+</I>&gt;<i> gstreamer0.10-rtmp
+</I>&gt;<i> gstreamer0.10-nas
+</I>&gt;<i> gstreamer0.10-rsvg
+</I>&gt;<i> gstreamer0.10-soundtouch
+</I>&gt;<i> gstreamer0.10-musepack
+</I>&gt;<i> gstreamer0.10-gsm
+</I>&gt;<i> gstreamer0.10-resindvd
+</I>&gt;<i> gstreamer0.10-kate
+</I>&gt;<i> gstreamer0.10-neon
+</I>&gt;<i> gstreamer0.10-voip
+</I>&gt;<i> gstreamer0.10-jp2k
+</I>&gt;<i> gstreamer0.10-ladspa
+</I>&gt;<i> gstreamer0.10-plugins-bad-doc
+</I>&gt;<i> gstreamer0.10-plugins-bad
+</I>&gt;<i> gstreamer0.10-celt
+</I>&gt;<i> gstreamer0.10-schroedinger
+</I>&gt;<i> gstreamer0.10-mms
+</I>&gt;<i> gstreamer0.10-dc1394
+</I>&gt;<i> gstreamer0.10-directfb
+</I>&gt;<i> gstreamer0.10-dirac
+</I>&gt;<i> gstreamer0.10-ofa
+</I>&gt;<i> gstreamer0.10-wildmidi
+</I>&gt;<i> gstreamer0.10-gme
+</I>&gt;<i> gstreamer0.10-vdpau
+</I>&gt;<i> gstreamer0.10-mpeg2enc
+</I>&gt;<i> gstreamer0.10-vp8
+</I>&gt;<i> gstreamer0.10-cog
+</I>&gt;<i> gstreamer0.10-curl
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> (A bit off-topic, I think -nas should be deprecated, NAS doesn't seem
+</I>&gt;<i> that used lately?).
+</I>
+Yeah it is a bit of a grab-bag of stuff, but again, should we still just
+bundle everything together anyway and sod the extra disk space needed?
+It would be a lot simpler for users (&quot;oh you need $foo? sure, just
+installed -ugly/-bad&quot;) which is advise they can get direct from upstream
+without having to know our particular packaging quirks.
+
+As someone who does upstream support for other projects, it's a pain to
+put caveats in all your advice for distros you don't know.
+
+That said, the trade off may be too much, hence the canvassing of
+opinions here :)
+
+Col
+
+
+
+
+
+--
+
+Colin Guthrie
+mageia(at)colin.guthr.ie
+<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
+
+Day Job:
+ Tribalogic Limited [<A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>]
+Open Source:
+ Mageia Contributor [<A HREF="http://www.mageia.org/">http://www.mageia.org/</A>]
+ PulseAudio Hacker [<A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>]
+ Trac Hacker [<A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>]
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="006365.html">[Mageia-dev] gstreamer packaging too split?
+</A></li>
+ <LI>Next message: <A HREF="006406.html">[Mageia-dev] gstreamer packaging too split?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6403">[ date ]</a>
+ <a href="thread.html#6403">[ thread ]</a>
+ <a href="subject.html#6403">[ subject ]</a>
+ <a href="author.html#6403">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>