From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
WeiLiu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: when to bump library versions (was: <blank>)
Date: Thu, 19 May 2016 16:53:36 +0200 [thread overview]
Message-ID: <20160519145336.ug3ysll2tzw4aupk@mac> (raw)
In-Reply-To: <573DED8B02000078000ECFB6@prv-mh.provo.novell.com>
On Thu, May 19, 2016 at 08:44:59AM -0600, Jan Beulich wrote:
> >>> On 19.05.16 at 16:34, <roger.pau@citrix.com> wrote:
> > Currently we bump the shared library names just before the release, so ATM
> > xen-unstable is still using the library names from the 4.6 release. This is
> > an issue if someone wants to install both Xen 4.6 and xen-unstable in the
> > same box (unless you use a different prefix/DESTDIR), because libraries from
> > xen-unstable will replace the stable ones.
> >
> > IMHO, it would make more sense to bump the library names just *after* we
> > branch and open the tree for development again.
>
> As you may have seen in Wei's recent commit, not all libraries have
> their versions bumped for a given release.
IMHO, I would make them all bump, regardless of whether there have been
changes or not.
> > We could even have the
> > library name versions be set based on XEN_VERSION and XEN_SUBVERSION, so
> > that we don't need to go around the different library makefiles bumping the
> > versions manually.
>
> But so far these two are intentionally private to the xen/ subtree.
Maybe I'm missing something, but couldn't they be global to the whole tree?
(Config.mk seems like a suitable place).
Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-19 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 14:34 (no subject) Roger Pau Monné
2016-05-19 14:44 ` when to bump library versions (was: <blank>) Jan Beulich
2016-05-19 14:53 ` Roger Pau Monné [this message]
2016-05-19 15:01 ` Jan Beulich
2016-05-23 11:06 ` George Dunlap
2016-06-06 12:33 ` Wei Liu
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=20160519145336.ug3ysll2tzw4aupk@mac \
--to=roger.pau@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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;
as well as URLs for NNTP newsgroup(s).