[opensuse-packaging] A "Sanitizing sources" with pre_checkin.sh question.
Hi, when I first started maintaining blender it had a pre-checkin.sh to remove it's built in ffmpeg, x264 and other banned items, from it's source. I was very happy when it was stated on the blender devel list that 2.5x would no longer have these but now I've found internal blender sources with ffmpeg in the name. Blender builds either "WITH_FFMPEG=yes" or "WITH_FFMPEG=no" does this mean that I now have to reinstate a pre_checkin.sh? The old blender-2.49b src rpm contains both the full and sanitized blender tarballs so I really don't understand the logic of it all. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Fri, Oct 29, 2010 at 02:53:41PM +0200, Dave Plater wrote:
Hi, when I first started maintaining blender it had a pre-checkin.sh to remove it's built in ffmpeg, x264 and other banned items, from it's source. I was very happy when it was stated on the blender devel list that 2.5x would no longer have these but now I've found internal blender sources with ffmpeg in the name. Blender builds either "WITH_FFMPEG=yes" or "WITH_FFMPEG=no" does this mean that I now have to reinstate a pre_checkin.sh? The old blender-2.49b src rpm contains both the full and sanitized blender tarballs so I really don't understand the logic of it all.
We cannot ship the "bad" sources, so it needs to be filtered in away that it does not land in the .src.rpm. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (2)
-
Dave Plater -
Marcus Meissner