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