On Wed, Nov 02, 2011 at 01:25:27PM +0100, Reinhard Tartler wrote: > On Mi, Nov 02, 2011 at 13:14:49 (CET), Martin Storsjö wrote: > > On Wed, 2 Nov 2011, Diego Biurrun wrote: > > > >> --- > >> configure | 21 +-------------------- > >> libavutil/internal.h | 28 ---------------------------- > >> 2 files changed, 1 insertions(+), 48 deletions(-) > > > > This is useful whenever we move public functions from one library to > > another. Currently, there are no such ones, since the cases where it was > > used was removed after the last major bump, but if we want to move more > > functions in an upcoming bump, we'll need this again.
How often does this really happen? > > Sure, we could just revert the removal if we need to move other > > functions again, of course, but removing it breaks scripts that use > > --disable-symver for the periods of time when it isn't present. I wouldn't mind putting it back if/when the need for it arises again. Note that in the meantime it confuses Doxygen into issuing warnings. > We should at least deprecate that configure switch for one release > before actually removing them. We've never handled configure switches in this way before. Diego _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
