public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] is there any value to FILESPATHPKG?
Date: Mon, 04 May 2020 16:53:43 +0100	[thread overview]
Message-ID: <bdccbf3d0baa5252b9738cca6b6b93b7c06eee53.camel@linuxfoundation.org> (raw)
In-Reply-To: <e9cb896b5db64c9bbb464cd66ec2e344@XBOX03.axis.com>

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


      reply	other threads:[~2020-05-04 15:53 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 ` [OE-core] " Peter Kjellerstedt
2020-05-04 15:53   ` Richard Purdie [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=bdccbf3d0baa5252b9738cca6b6b93b7c06eee53.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --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