>> > https://bugs.gentoo.org/show_bug.cgi?id=363631 >> > >> >> >> 2011, that's quite old. > > Apparently no one cared (enough). Now you do. > >> I'm not quite sure what the next thing to do is. >> Should I add a comment on bugs.gentoo.org or do we discuss it here. > > I don't see what you mean by "here". You didn't CC the developer > mailing list this time. > > The developer mailing list is for more general development issues and > discussion thereof, whereas the bug tracker is intended for > package-specific issues. So obviously you shouldn't be addressing > "everyone" (all aliased on the developer mailing list alias) where you > want to address "gstreamer maintainers" (on the bug tracker). > > The best way forward is probably to 1) comment on the aforementioned > bug report and 2) file a new bug report requesting a gst-plugins-shm > ebuild, perhaps blocking that other bug report. > Thanks. I'll do that. I had a look at the output of ./configure --help with gst-plugins-bad-1.6.2 and there is not "--enable-shm". There is just a "--disable-shm". I don't know if a new ebuild gst-plugins-shm is possible. So, the gst-plugins-bad-1.6.2 ebuild will have to be modified. I am new to writing ebuilds. I'm not sure if this is correct.
Thanks Mandar Joshi
