Hi, I think is better increase the REVISION number instead of the WINGS_CURRENT when we are *adding* new functions. The new revision has backward compatibility with previous versions of wmaker, so IMO is better hold the library version number. We should avoid remove functions, because other applications could use them.
OTOH IMO we should change the library version number only one time in every wmaker release. Cheers, kix On Fri, 05 Dec 2014, David Maciejak escribió: > This patch is incrementing version number as the API changed. > > --- > configure.ac | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/configure.ac b/configure.ac > index 7097e9d..1dbba92 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -47,7 +47,7 @@ > WRASTER_VERSION=$WRASTER_CURRENT:$WRASTER_REVISION:$WRASTER_AGE > AC_SUBST(WRASTER_VERSION) > dnl > dnl libWINGs > -WINGS_CURRENT=3 > +WINGS_CURRENT=4 > WINGS_REVISION=0 > WINGS_AGE=0 > WINGS_VERSION=$WINGS_CURRENT:$WINGS_REVISION:$WINGS_AGE > -- > 2.1.0 > > On Thu, Dec 4, 2014 at 5:47 PM, Alexey I. Froloff <ra...@raorn.name> wrote: > > On Thu, Dec 04, 2014 at 04:08:41PM +0800, David Maciejak wrote: > >> +void WMSetWidgetBackgroundPixmap(WMWidget *w, WMPixmap *pix); > >> + > >> +WMPixmap *WMGetWidgetBackgroundPixmap(WMWidget *w); > >> + > > New public functions are added to the library. WINGS_VERSION > > should be changed as described in info libtool (Updating version > > info) - increment WINGS_CURRENT and set WINGS_REVISION to 0. > > > > -- > > Regards, -- > > Sir Raorn. --- https://plus.google.com/+AlexeyFroloff -- ||// //\\// Rodolfo "kix" Garcia ||\\// //\\ http://www.kix.es/ -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
