From: Michael Tretter <m.tretter@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 3/4] weston: version bump 3.0.0 -> 4.0.0
Date: Tue, 10 Apr 2018 17:31:11 +0200 [thread overview]
Message-ID: <20180410173111.0cd756af@litschi.hi.pengutronix.de> (raw)
In-Reply-To: <1523372391.3372.1.camel@pengutronix.de>
On Tue, 10 Apr 2018 16:59:51 +0200, Philipp Zabel wrote:
> On Tue, 2018-04-10 at 16:27 +0200, Michael Olbrich wrote:
> > On Tue, Apr 10, 2018 at 11:06:46AM +0200, Michael Tretter wrote:
> > > Split the version into major.minor.pl and use variable instead of hard
> > > coded version for installing libweston.
> > >
> > > Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> > > ---
> > > rules/weston.in | 1 -
> > > rules/weston.make | 26 ++++++++++++++------------
> > > 2 files changed, 14 insertions(+), 13 deletions(-)
> > >
> > > diff --git a/rules/weston.in b/rules/weston.in
> > > index 7db255202..a1755f510 100644
> > > --- a/rules/weston.in
> > > +++ b/rules/weston.in
> > > @@ -13,7 +13,6 @@ menuconfig WESTON
> > > select CAIRO
> > > select CAIRO_PNG
> > > select LIBDRM if WESTON_DRM_COMPOSITOR
> > > - select MTDEV if WESTON_DRM_COMPOSITOR || WESTON_FBDEV_COMPOSITOR
> > > select UDEV if WESTON_DRM_COMPOSITOR || WESTON_FBDEV_COMPOSITOR
> > > select UDEV_LIBUDEV if WESTON_DRM_COMPOSITOR || WESTON_FBDEV_COMPOSITOR
> > > select MESALIB if WESTON_DRM_COMPOSITOR
> > > diff --git a/rules/weston.make b/rules/weston.make
> > > index 6e7065982..06175a304 100644
> > > --- a/rules/weston.make
> > > +++ b/rules/weston.make
> > > @@ -17,8 +17,11 @@ PACKAGES-$(PTXCONF_WESTON) += weston
> > > #
> > > # Paths and names
> > > #
> > > -WESTON_VERSION := 3.0.0
> > > -WESTON_MD5 := 9c42a4c51a1b9f35d040fa9d45ada36d
> > > +WESTON_MAJOR := 4
> > > +WESTON_MINOR := 0
> > > +WESTON_PL := 0
> > > +WESTON_VERSION := $(WESTON_MAJOR).$(WESTON_MINOR).$(WESTON_PL)
> >
> > I prefer the version in one line. And use this for the major version:
> >
> > WESTON_MAJOR := $(basename $(basename $(WESTON_VERSION)))
>
> The library version below is LIBWESTON_MAJOR in configure.ac, not
> WESTON_VERSION_MAJOR. Both currently have the same value, but will
> weston increase major version with every backwards incompatible
> libweston API change? How about:
>
> WESTON_VERSION := 4.0.0
> LIBWESTON_MAJOR := 4
I see. Actually the LIBWESTON_MAJOR changes with the first ABI
break, while WESTON_VERSION changes with the release and they are only
for releases and more or less by coincidence the same. I'll split the
variables.
Michael
>
> regards
> Philipp
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-04-10 15:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 9:06 [ptxdist] [PATCH 1/4] wayland-protocols: version bump 1.12 -> 1.13 Michael Tretter
2018-04-10 9:06 ` [ptxdist] [PATCH 2/4] wayland: version bump 1.14 -> 1.15 Michael Tretter
2018-04-10 9:06 ` [ptxdist] [PATCH 3/4] weston: version bump 3.0.0 -> 4.0.0 Michael Tretter
2018-04-10 14:27 ` Michael Olbrich
2018-04-10 14:59 ` Philipp Zabel
2018-04-10 15:31 ` Michael Tretter [this message]
2018-04-10 9:06 ` [ptxdist] [PATCH 4/4] weston: make dbus and weston-launch configurable Michael Tretter
2018-04-10 14:31 ` Michael Olbrich
2018-04-10 15:26 ` Michael Tretter
2018-04-11 10:03 ` [ptxdist] [PATCH v2 0/4] wayland, weston: version bump Michael Tretter
2018-04-11 10:03 ` [ptxdist] [PATCH v2 1/4] wayland-protocols: version bump 1.12 -> 1.13 Michael Tretter
2018-04-11 10:03 ` [ptxdist] [PATCH v2 2/4] wayland: version bump 1.14 -> 1.15 Michael Tretter
2018-04-11 10:03 ` [ptxdist] [PATCH v2 3/4] weston: version bump 3.0.0 -> 4.0.0 Michael Tretter
2018-04-11 10:03 ` [ptxdist] [PATCH v2 4/4] weston: make weston-launch configurable Michael Tretter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180410173111.0cd756af@litschi.hi.pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox