All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Koehler, Yannick" <yannick.koehler@hpe.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: bbappend - FILESEXTRAPATHS
Date: Fri, 20 Oct 2017 09:39:14 -0500	[thread overview]
Message-ID: <20171020093914.f166839216341ff7537df01b@linux.intel.com> (raw)
In-Reply-To: <TU4PR84MB01764E055DD6B5F1BBC43003ED430@TU4PR84MB0176.NAMPRD84.PROD.OUTLOOK.COM>

On Fri, 20 Oct 2017 13:30:06 +0000
"Koehler, Yannick" <yannick.koehler@hpe.com> wrote:

> Hi,
> 
>  
> 
> I have been using Yocto for over 2 years now, and whenever I create a new
> bbappend file, I always have to remember that FILESEXTRAPATHS variable,
> often typing it wrong, EXTRAFILESPATHS or FILEEXTRAPATHS or FILESEXTRAPATH,
> etc.
> 
>  
> 
> I did a quick check on my setup and on 102 bbappend recipe found, there are
> 73 that uses the FILESEXTRAPATHS variable, so that is around 71% of them.  
> 
>  
> 
> I was wondering if the team would enhance the user/dev experience here and
> modify bitbake behavior as to not require this variable and be able to
> "override" any FILESPATH that already exists with the bbappend location.  So
> that for example the FILESPATH "files" would be looked up in the bbappend
> folder location before the initial bb recipe folder location automatically
> without having to manually enter a FILESEXTRAPATHS statement.

One easy way to avoid this error is to place the FILESEXTRAPATHS variable inside a custom bbclass them inherit it from the recipe, at least it is less prone to typos. We do not want to force users to place patches inside a particular folder (policy), instead the system offer a mechanism to place these any place you want (other recipes choose PN, for example)

> 
>  
> 
> Or alternatively, a script or command to create an initial skeleton bbappend
> with the initial .bb in comment 
> 
>  
> 
>                bbappend mylayer recipename.bb
> 
>                # Create a file under mylayer/recipes-*/*.bbappend (using %
> for version when not specified on cmd line) with the original .bb in comment
> and a section containing FILESEXTRAPATHS
> 

Right, I think there is no tool to create bbappends from the command line.

Anyway, feel free to file a bug (bugzilla.yoctoproject.org) with your enhancement.


>  
> 
> I think this would greatly help when creating those files.
> 
>  
> 
> --
> 
> Yannick Koehler
> 
> HPE Aruba
> 


-- 
Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>


  parent reply	other threads:[~2017-10-20 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 13:30 bbappend - FILESEXTRAPATHS Koehler, Yannick
2017-10-20 14:10 ` Joshua Watt
2017-10-20 14:39 ` Leonardo Sandoval [this message]
2017-10-20 17:15   ` Koehler, Yannick

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=20171020093914.f166839216341ff7537df01b@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=yannick.koehler@hpe.com \
    --cc=yocto@yoctoproject.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.