Changing kernel API / Breaking VirtualBox - update criteria violation?

Stijn Hoop stijn at sandcat.nl
Thu Dec 8 20:10:28 UTC 2011


On Thu, 08 Dec 2011 19:02:26 +0100
Reindl Harald <h.reindl at thelounge.net> wrote:
> Am 08.12.2011 17:04, schrieb Kevin Kofler:
> > Reindl Harald wrote:
> >> my only changes was compile the x264.119 and fake the so-number
> >> in the sources to .102 for F13/F14 and to .114/.115 for F15
> >> and currently the .120 to 115
> > 
> > Changing soversions is a very bad idea, upstream probably bumped
> > them for a reason.
> 
> i know and that is why this are private builds
> 
> doe snot change the fact that rpmfusion did a so-bump on x264
> with all the needed rebuilds and bumped only from 114 to 115
> instead 119 while all this apps are working even with 120
> perfectly
> 
> they stayed for nearly 2 years at x264.so.102 what makes
> compile of newer ffmpeg impossible and so i see not that
> big glory in the rpmfusion packages since they also never
> do the fedora-massrebuilds after GLIBC/GCC changes at
> their side
> 
> be happy with it - for me the packages are only a nice
> "to start with"-SPEC

I think you'll find out that either

- bumping to .120 makes some other programs not work anymore
- they don't have enough manpower to do the proper rebuilds

Both of which are solvable problems given more manpower and/or
expertise, which you seem to have but chose to invest only privately.

Which is fine by me, but then please do not complain about the people
who DO share their time, on this list.

Regards,

--Stijn


More information about the devel mailing list