From: Denys Dmytriyenko <denys@ti.com>
To: "Stiffler, Jacob" <j-stiffler@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [PATCH] systemd: provide symlink to libudev.so.0, required by SGX libs/bins
Date: Tue, 10 May 2016 15:13:45 -0400 [thread overview]
Message-ID: <20160510191345.GJ16188@edge> (raw)
In-Reply-To: <f9be806e-8324-4b97-a889-c7028746ca0e@email.android.com>
I'm back at the keyboard, so a bit of clarification. I've been doing distros
for at least 20 years and OpenEmbedded for almost 10. I was right in the
middle of it, when the original OE versioning policy was drafted. At the time,
Arago Project has already started using -nameX suffix with Classic OE. I know
we agreed then that in general PR should not contain dashes, although there
were some specific use cases. Since then it was mostly a matter of habit, but
I've been meaning to start switching over to using dots instead of dashes.
As of PR service - for short-lived bbappends it wouldn't matter much, as you
are going to hit the problem of the version going backwards sooner or later.
Either when you add a bbappend with modified PR, or when you remove it... The
cleanest solution, as a matter of fact, is to NOT modify PR at all and let PR
service figure it out. There are some pitfalls in that approach and for better
results a centralized distributed PR service is preferred over a local one,
especially when doing many distributed builds like we do. That's why I have a
dedicated PR service in the new build infrastructure I'm building... We should
probably connect you and your builds to that one in the future, especially
since we are thinking of package feeds and maintaining upgrade path across
releases.
--
Denys
On Tue, May 10, 2016 at 02:32:34PM +0000, Dmytriyenko, Denys wrote:
> I know
>
> > -----Original Message-----
> > From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> > bounces@arago-project.org] On Behalf Of Denys Dmytriyenko
> > Sent: Monday, May 09, 2016 10:09 AM
> > To: meta-arago@arago-project.org
> > Subject: [meta-arago] [PATCH] systemd: provide symlink to libudev.so.0,
> > required by SGX libs/bins
> >
> > From: Denys Dmytriyenko <denys@ti.com>
> >
> > eudev and systemd bumped major version number to libudev.so.1, but SGX
> > has
> > version 0 hardcoded. Symlink for now, until binaries can be rebuilt.
> >
> > Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> > ---
> > meta-arago-distro/recipes-core/systemd/systemd_%.bbappend | 6 ++++++
> > 1 file changed, 6 insertions(+)
> > create mode 100644 meta-arago-distro/recipes-
> > core/systemd/systemd_%.bbappend
> >
> > diff --git a/meta-arago-distro/recipes-core/systemd/systemd_%.bbappend
> > b/meta-arago-distro/recipes-core/systemd/systemd_%.bbappend
> > new file mode 100644
> > index 0000000..05c8e34
> > --- /dev/null
> > +++ b/meta-arago-distro/recipes-core/systemd/systemd_%.bbappend
> > @@ -0,0 +1,6 @@
> > +PR_append = "-arago0"
>
> PR_append should begin with a ".", not a "-". Otherwise builds with PR
> service, and buildhistory will fail as the version goes backwards.
> http://www.openembedded.org/wiki/Versioning_Policy
>
> > +
> > +do_install_append() {
> > + install -d ${D}/${base_libdir}
> > + ln -sf libudev.so.1 ${D}${base_libdir}/libudev.so.0
> > +}
> > --
> > 2.2.0
> >
> > _______________________________________________
> > meta-arago mailing list
> > meta-arago@arago-project.org
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
prev parent reply other threads:[~2016-05-10 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 14:08 [PATCH] systemd: provide symlink to libudev.so.0, required by SGX libs/bins Denys Dmytriyenko
2016-05-10 14:14 ` Stiffler, Jacob
2016-05-10 14:32 ` Dmytriyenko, Denys
2016-05-10 19:13 ` Denys Dmytriyenko [this message]
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=20160510191345.GJ16188@edge \
--to=denys@ti.com \
--cc=j-stiffler@ti.com \
--cc=meta-arago@arago-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.