On 01/31/2011 11:21 AM, Ludwig Nussel wrote:

Dave Plater wrote:

...

My proposal is take gstreamer out of multimedia and (I see GNOME:Factory already has it) move it to where somebody cares about it in kde.

You could also found a new, separate devel project that only contains the gstreamer components.

cu Ludwig

Yesterday evening I broke my reading glasses they are 1.75x and had to wear a pair of 3x glasses that I use for fine electronic work and they give me a headache. I went through gstreamer for the first time and almost all it's dependencies are in multimedia:libs so there it stays, gst-rstp should move to kde4 where it's cousins python-gstreamer live and an up to date gstreamer should normally be found. When I've composed a story for why lv2core and slv2 should go to factory and sent them on their way I'll put in a move devel request for gst-rstp. Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On 01/31/2011 12:21 PM, Vincent Untz wrote:

Le lundi 31 janvier 2011, à 11:54 +0200, Dave Plater a écrit :

...

gst-rstp should move to kde4 where it's cousins python-gstreamer live and an up to date gstreamer should normally be found.

I'm not quite sure why you want to move to KDE projects packages that are maintained by the GNOME team ;-) More seriously: gst-rtsp extends gstreamer, so it should really just live with gstreamer, imho.

Note that if you prefer to ignore gstreamer when maintaining m:l, it's fine: at least the GNOME team is actively maintaining the packages for Factory, and various other people have contributed to it in the past (to fix issues on older distributions, or to build new plugins, eg).

Vincent

I've noticed that you maintain them, tell me why does python-gstreamer-0_10 live in kde4? gst-rstp should be with it in gnome as it depends on at least one gnome package and afaics no kde specific ones, if it's needed specifically for kde4 then kde4 should link to it. btw I've just updated plugins-bad, I'll put instructions in the spec file on how to use the pre_checkin. I think the only thing that really bothered me was the hermes spam from the < factory packages failing, I've solved that by disabling the build for them. Gstreamer packages that depend on mostly mmlibs packages should stay where they are. Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On 01/31/2011 01:51 PM, Vincent Untz wrote:

Le lundi 31 janvier 2011, à 13:23 +0200, Dave Plater a écrit :

...

On 01/31/2011 12:21 PM, Vincent Untz wrote:

...

Le lundi 31 janvier 2011, à 11:54 +0200, Dave Plater a écrit :

...

gst-rstp should move to kde4 where it's cousins python-gstreamer live and an up to date gstreamer should normally be found.

I'm not quite sure why you want to move to KDE projects packages that are maintained by the GNOME team ;-) More seriously: gst-rtsp extends gstreamer, so it should really just live with gstreamer, imho.

Note that if you prefer to ignore gstreamer when maintaining m:l, it's fine: at least the GNOME team is actively maintaining the packages for Factory, and various other people have contributed to it in the past (to fix issues on older distributions, or to build new plugins, eg).

I've noticed that you maintain them, tell me why does python-gstreamer-0_10 live in kde4?

No idea. I believe various packages are linked in the KDE projects, because they are needed for backports, so that could explain it.

...

gst-rstp should be with it in gnome as it depends on at least one gnome package and afaics no kde specific ones, if it's needed specifically for kde4 then kde4 should link to it.

I guess you mean vala, gobject-introspection or python-gobject? Why is it bad?

...

btw I've just updated plugins-bad, I'll put instructions in the spec file on how to use the pre_checkin.

Cool, thanks!

Vincent

Well not really it's not building :-( :- /usr/lib64/gstreamer-0.10/libgstalsaspdif.so /usr/lib64/gstreamer-0.10/libgstjack.so /usr/lib64/gstreamer-0.10/libgstmetadata.so /usr/lib64/gstreamer-0.10/libgstselector.so /usr/lib64/gstreamer-0.10/libgstvalve.so Which I'm looking into before I take them off the files list, there were a few extra source directories to examine and add to the allowed list. Good and ugly plugins also have updates waiting in line. A good chance for me to get to know gstreamer. Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Quoting Dave Plater :

...

On 01/31/2011 01:51 PM, Vincent Untz wrote:

...

Well not really it's not building :-( :- /usr/lib64/gstreamer-0.10/libgstalsaspdif.so /usr/lib64/gstreamer-0.10/libgstjack.so /usr/lib64/gstreamer-0.10/libgstmetadata.so /usr/lib64/gstreamer-0.10/libgstselector.so /usr/lib64/gstreamer-0.10/libgstvalve.so

Which I'm looking into before I take them off the files list, there were a few extra source directories to examine and add to the allowed list. Good and ugly plugins also have updates waiting in line. A good chance for me to get to know gstreamer.

The latest releases moved some plugins around, so the missing files might pop up in a different plugin set now..

Make sure to carefully read the release notes: such changes are typically mentioned by the devs.

If it's too much for you, just leave the gst packages and we'll take care of them (prioritized for Factory normally... that's where we want them most)

Dominique That's useful information, I need to familiarise myself with the gstreamer family. The changelog should indicate if the plugins have been moved or at least git or svn whichever they use. I also see the build looking for other gstreamer plugin flavours. > a certain version. It's given me another package that uses the LV2 plugin system and a chance to test build. Rpmbuild checks for "file not found" before "file not installed". I'm still busy composing a good reason for slv2 and lv2core to go to factory, I got distracted far to much by redland-perl installing in site_arch, the package only needed the python bindings and so far all

On 01/31/2011 05:44 PM, Dominique Leuenberger a.k.a DimStar wrote: the packages I've built with LV2 don't use lv2-config, I could have left it out. Thanks Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Le lundi 31 janvier 2011, à 21:30 +0200, Dave Plater a écrit :

It's a bit risky when plugins play musical chairs with packages, you obviously have to update all the gstreamers together or not at all.

Yes. Which is why I asked darix^Wthe autobuild team to not accept the new gstreamer and gstreamer-plugins-base at the moment: it's all or nothing. Another reason to update them all at once is that upstream tests all the new versions together, but not a mix of old and new versions. So we might get interesting bugs if we have a mix. Cheers, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org