From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] git: add site_perl to packaged files to fix QA install error
Date: Mon, 1 Feb 2016 13:11:39 -0500 [thread overview]
Message-ID: <20160201181138.GF8889@windriver.com> (raw)
In-Reply-To: <1454276439.7421.28.camel@pbcl.net>
[Re: [OE-core] [PATCH] git: add site_perl to packaged files to fix QA install error] On 31/01/2016 (Sun 21:40) Phil Blundell wrote:
> On Sun, 2016-01-31 at 13:27 -0500, Paul Gortmaker wrote:
> > FILES_${PN}-perltools += " \
> > ${PERLTOOLS} \
> > ${libdir}/perl \
> > + ${libdir}/site_perl \
> > ${datadir}/perl \
>
> It seems a bit wrong for git (or any other package) to be installing
> itself into site-perl. That path is meant to be for stuff installed
> locally via cpan, right?
I'm not up to speed on perl/cpan specs, but yeah off the cuff it does
seem rather odd for it to be sprawling out into any perl dir IMHO.
Even the perl bb itself seems to actively clobber site_perl for the
non native case.
>
> So, rather than patching the FILES to accept site-perl I think it would
> be better to find out why git is suddenly putting stuff there and stop
Interestingly enough, you won't find site_perl mentioned anywhere in a
checkout of git 2.7 itself. Nor does it appear here:
paul@yow-cube1:~/poky/meta/recipes-devtools/git$ git grep site_perl ./
paul@yow-cube1:~/poky/meta/recipes-devtools/git$
I'd reverted the git uprev, no change. There was a perl uprev that was
recent and I reverted that too as a test but no change. Unfortunately
I'm not exactly sure when it got broke, so I'd probably just have to
guess and go back a week or two, if I wanted to try and bisect it.
> it. For what it's worth, I just built git from oe-core master and
> didn't see this problem so it's possible that the breakage is being
> caused by something outside oe-core itself.
Interesting. I've not got any local bbappends for git so I don't know
what is the trigger. I'm guessing SVN is perhaps involved, since all
the "extra" files are related to git-svn. And I'm loosely based on the
self-hosting build appliance here, which IIRC has svn in the pkglist.
So maybe that triggers git to do additional svn import features?
I'm going to locally bbappend do_install to clobber that crap, and in
the meantime if I get a chance to investigate in more detail, I'll
follow up with what I find. At least we've primed google for the next
guy who runs into this and searches...
P.
--
>
> p.
>
>
next prev parent reply other threads:[~2016-02-01 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 18:27 [PATCH] git: add site_perl to packaged files to fix QA install error Paul Gortmaker
2016-01-31 21:40 ` Phil Blundell
2016-02-01 18:11 ` Paul Gortmaker [this message]
2016-02-01 21:16 ` Burton, Ross
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=20160201181138.GF8889@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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.