From: petter@technux.se
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/13] Remove usage of FILESPATH
Date: Thu, 08 May 2014 06:37:58 +0200 [thread overview]
Message-ID: <f90bcdd0b14a8029f93fd41a400da185@technux.se> (raw)
In-Reply-To: <1399501262.31891.42.camel@ted>
2014-05-08 00:21 skrev Richard Purdie:
> On Wed, 2014-05-07 at 23:19 +0200, Petter Mabäcker wrote:
>
>> Fixes [YOCTO #4497] We extend the search path in a number of recipes
>> by
>> setting FILESPATH, which is not really desirable since the manner in
>> which we have done it can make the recipe harder to bbappend (and we
>> explicitly advise modifying FILESPATH this in the manual). These
>> should
>> be changed to use FILESEXTRAPATHS to extend the path instead or use
>> a
>> default FILESPATH (e.g. BP, BPN or files).
>
> Whilst FILESPATH is discouraged, so is putting files into "files"
> directories so those changes are not an improvement.
>
> Cheers,
>
> Richard
I agree, 'files' is not a good choice and of course BP and BPN are
preferred if possible. My intention in this case however was that
'files' was an "less bad" option in the situations where all bb-files
within a recipe used a 'common' dir to store patches. In these
situations I thought it was more clear to use a name that better
displayed the "common use" and since 'files' is quite a common name +
that it removes the need of extending the filespath, I used it in theses
situations. But I guess you could see 'BPN' as a common dir as well
since it's the same name as the recipe (even if they are used by other
bb-files with different PN within the same recipe). So I will change
those commits that are using 'files' and use either BPN as a "shared
patchdir" or try to split them into different PN/P dirs if possible.
BR,
Petter
prev parent reply other threads:[~2014-05-08 4:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 21:19 [PATCH 00/13] Remove usage of FILESPATH Petter Mabäcker
2014-05-07 21:19 ` [PATCH 01/13] systemtap: remove " Petter Mabäcker
2014-05-07 21:19 ` [PATCH 02/13] dbus: " Petter Mabäcker
2014-05-07 21:19 ` [PATCH 03/13] gstreamer: remove unused FILESPATH Petter Mabäcker
2014-05-07 21:19 ` [PATCH 04/13] trace-cmd: remove usage of FILESPATH Petter Mabäcker
2014-05-08 10:46 ` Martin Jansa
2014-05-08 14:56 ` petter
2014-05-07 21:19 ` [PATCH 05/13] xorg-lib: " Petter Mabäcker
2014-05-07 21:19 ` [PATCH 06/13] mesa: " Petter Mabäcker
2014-05-08 10:49 ` Martin Jansa
2014-05-09 5:11 ` petter
2014-05-07 21:19 ` [PATCH 07/13] qemu: remove unused FILESPATH Petter Mabäcker
2014-05-07 21:19 ` [PATCH 08/13] linuxdoc-tools: remove usage of FILESPATH Petter Mabäcker
2014-05-08 10:50 ` Martin Jansa
2014-05-08 14:48 ` petter
2014-05-07 21:19 ` [PATCH 09/13] gcc: " Petter Mabäcker
2014-05-07 21:19 ` [PATCH 10/13] python: " Petter Mabäcker
2014-05-08 10:53 ` Martin Jansa
2014-05-09 4:53 ` petter
2014-05-07 21:19 ` [PATCH 11/13] u-boot: remove unused FILESPATH Petter Mabäcker
2014-05-07 21:19 ` [PATCH 12/13] uclibc: remove usage of FILESPATH Petter Mabäcker
2014-05-07 21:19 ` [PATCH 13/13] eglibc: " Petter Mabäcker
2014-05-07 22:21 ` [PATCH 00/13] Remove " Richard Purdie
2014-05-08 4:37 ` petter [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=f90bcdd0b14a8029f93fd41a400da185@technux.se \
--to=petter@technux.se \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 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.