From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] is there any value to FILESPATHPKG?
Date: Mon, 4 May 2020 13:29:40 +0000 [thread overview]
Message-ID: <e9cb896b5db64c9bbb464cd66ec2e344@XBOX03.axis.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2005040611490.6242@localhost.localdomain>
> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Robert P. J. Day
> Sent: den 4 maj 2020 12:14
> To: OE Core mailing list <openembedded-core@lists.openembedded.org>
> Subject: [OE-core] is there any value to FILESPATHPKG?
>
> not sure where i read this (YP overview manual?), but i recall
> something about the FILESPATHPKG variable being deprecated, and i see
> its only references are:
>
> $ grep -irw filespathpkg *
> meta/classes/utils.bbclass: filespathpkg = d.getVar("FILESPATHPKG").split(":")
> meta/classes/utils.bbclass: for pkgpath in filespathpkg:
> $
>
> so i'll leave it to someone else to decide if it still has value.
>
> rday
A quick grep through the Git logs for Poky and Openembedded
indicates that the only functions that depend on FILESPATHPKG,
is_machine_specific() and machine_paths(), have never been used
since their introduction. So I'd say it should be safe to remove
them.
//Peter
next prev parent reply other threads:[~2020-05-04 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 10:13 is there any value to FILESPATHPKG? Robert P. J. Day
2020-05-04 13:29 ` Peter Kjellerstedt [this message]
2020-05-04 15:53 ` [OE-core] " Richard Purdie
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=e9cb896b5db64c9bbb464cd66ec2e344@XBOX03.axis.com \
--to=peter.kjellerstedt@axis.com \
--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