Mailinglist Archive: opensuse-packaging (214 mails)
| < Previous | Next > |
[opensuse-packaging] A "Sanitizing sources" with pre_checkin.sh question.
- From: Dave Plater <davejplater@xxxxxxxxx>
- Date: Fri, 29 Oct 2010 14:53:41 +0200
- Message-id: <4CCAC3D5.3090306@xxxxxxxxx>
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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
| < Previous | Next > |