* is there any value to FILESPATHPKG?
@ 2020-05-04 10:13 Robert P. J. Day
2020-05-04 13:29 ` [OE-core] " Peter Kjellerstedt
0 siblings, 1 reply; 3+ messages in thread
From: Robert P. J. Day @ 2020-05-04 10:13 UTC (permalink / raw)
To: OE Core mailing list
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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [OE-core] is there any value to FILESPATHPKG?
2020-05-04 10:13 is there any value to FILESPATHPKG? Robert P. J. Day
@ 2020-05-04 13:29 ` Peter Kjellerstedt
2020-05-04 15:53 ` Richard Purdie
0 siblings, 1 reply; 3+ messages in thread
From: Peter Kjellerstedt @ 2020-05-04 13:29 UTC (permalink / raw)
To: openembedded-core@lists.openembedded.org
> -----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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [OE-core] is there any value to FILESPATHPKG?
2020-05-04 13:29 ` [OE-core] " Peter Kjellerstedt
@ 2020-05-04 15:53 ` Richard Purdie
0 siblings, 0 replies; 3+ messages in thread
From: Richard Purdie @ 2020-05-04 15:53 UTC (permalink / raw)
To: openembedded-core
On Mon, 2020-05-04 at 13:29 +0000, Peter Kjellerstedt wrote:
> > -----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.
Agreed, I started thinking they'd be fine simplified, but I think it
does make most sense to remove them entirely.
Cheers,
Richard
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-05-04 15:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-05-04 10:13 is there any value to FILESPATHPKG? Robert P. J. Day
2020-05-04 13:29 ` [OE-core] " Peter Kjellerstedt
2020-05-04 15:53 ` Richard Purdie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox