From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/7] bitbake.conf: fix definition of ${libexecdir}
Date: Mon, 29 Apr 2013 17:52:07 +0200 [thread overview]
Message-ID: <lyip35jpw8.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CAJTo0Laf-d0hz5kkRZZAr7W4yGs+aYaTu51XU2k2q-s0p57q5A@mail.gmail.com> (Ross Burton's message of "Mon, 29 Apr 2013 16:33:37 +0100")
"Burton, Ross" <ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
writes:
> I agree with dropping $libdir and hard-coding "lib", but have you done
> a world oe-core build
no; I do not have the resources for this :( I did a static analysis of
recent recipes and fixed the obvious things.
Change will cause probably some silent breakage which can not be detected
by static analysis. E.g. the last /usr/libexec -> /usr/lib/${BPN} change
broke dropbear sftp which remained undetected for more than a half year.
We are at the beginning of a new release cycle which is a good time for
this change.
> with buildhistory to verify that nothing else moved around?
Things *are* expected to move around. E.g. /usr/lib/openssh/sftp-server
becomes /usr/lib/sftp-server now.
Enrico
next prev parent reply other threads:[~2013-04-29 16:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 15:26 [PATCH 1/7] bitbake.conf: fix definition of ${libexecdir} Enrico Scholz
2013-04-29 15:26 ` [PATCH 2/7] bitbake.conf: fix libexecdir packaging Enrico Scholz
2013-04-29 15:26 ` [PATCH 3/7] connman: " Enrico Scholz
2013-04-29 15:26 ` [PATCH 4/7] eglibc: " Enrico Scholz
2013-04-29 15:26 ` [PATCH 5/7] uclibc: " Enrico Scholz
2013-04-29 15:26 ` [PATCH 6/7] gstreamer: " Enrico Scholz
2013-04-29 15:26 ` [PATCH 7/7] gamin: " Enrico Scholz
2013-04-29 15:33 ` [PATCH 1/7] bitbake.conf: fix definition of ${libexecdir} Burton, Ross
2013-04-29 15:52 ` Enrico Scholz [this message]
2013-04-29 16:20 ` Burton, Ross
2013-04-29 17:03 ` Enrico Scholz
2013-04-29 22:33 ` Saul Wold
2013-04-29 23:15 ` Enrico Scholz
2013-04-30 9:34 ` Phil Blundell
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=lyip35jpw8.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.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