[PATCH weston] README: introduce libweston
ppaalanen at gmail.com
Wed Jul 15 00:12:46 PDT 2015
On Tue, 14 Jul 2015 13:13:26 -0700
Bryce Harrington <bryce at osg.samsung.com> wrote:
> On Tue, Jul 14, 2015 at 01:07:47PM +0300, Pekka Paalanen wrote:
> > From: Pekka Paalanen <pekka.paalanen at collabora.co.uk>
> > What is libweston and where do we intend to go with it.
> > Cc: Giulio Camuffo <giuliocamuffo at gmail.com>
> > Signed-off-by: Pekka Paalanen <pekka.paalanen at collabora.co.uk>
> > ---
> > README | 139 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> > 1 file changed, 138 insertions(+), 1 deletion(-)
> > +To make things tolerable for libweston users in spite of ABI
> s/in spite of/despite/ ? (not sure)
> > +breakages, libweston is designed to be perfectly parallel-installable.
> > +An ABI-version is defined for libweston, and it is bumped for releases
> > +as needed. Different ABI-versions of libweston can be installed in
> > +parallel, so that external projects can easily depend on a particular
> > +ABI-version, and they do not have to fight over which ABI-version is
> > +installed in a user's system.
> > +
> > +Note, that versions of Weston itself will not be parallel-installable,
> > +only libweston is.
> Do we need to give more of an explanation of what "parallel-installable"
> means, or can we expect our audience to generally know? Perhaps a short
> example file listing would be illustrative.
Maybe I'll add a link to http://ometer.com/parallel.html ?
But that's just details for libweston developers. What the end users
(people installing compositors that depend on libweston) care about is
that installing several different compositors at the same time is
possible, even if each of them requires a different ABI-version of
The complication here is that project Weston is not a single package
but essentially several, most importantly libweston vs. weston.
> Overall, very good declaration of intent for libweston and gives
> definitive answers to some of the questions that have been floating
> about. Apart from the trivial copyedits above, the scope and
> development approach sounds good to me:
> Reviewed-by: Bryce Harrington <bryce at osg.samsung.com>
Thanks! I'll make your suggested modifications if more people are happy
with this declaration's content.
I'm looking for Acked-by's so I can show that this is some sort of a
concensus rather than my own agenda. :-)
More information about the wayland-devel