Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Fix: stage hidden files as well
Date: Thu, 29 Apr 2010 09:05:31 +0200	[thread overview]
Message-ID: <hrbb3r$dkf$1@dough.gmane.org> (raw)
In-Reply-To: <z2jb6ebd0a51004281652pc34c3e99zb1b54788fd5213d3@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 29-04-10 01:52, Chris Larson wrote:
> On Wed, Apr 28, 2010 at 2:49 PM, Tom Rini <tom_rini@mentor.com> wrote:
> 
>> On Mon, 2010-04-26 at 11:24 -0500, Mike Westerhof wrote:
>>> The following patch is a proposed patch to fix the problem where hidden
>>> files are sometimes missed during staging.  A specific example is that
>>> the symbolic link ".config" is not copied to the kernel staging area,
>>> which causes madwifi-ng to fail to build.
>>>
>>> diff --git a/classes/staging.bbclass b/classes/staging.bbclass
>>> index 32038a5..cb19cb9 100644
>>> --- a/classes/staging.bbclass
>>> +++ b/classes/staging.bbclass
>>> @@ -35,6 +35,13 @@ sysroot_stage_dir() {
>>>         if [ -d "$src" ]; then
>>>                 mkdir -p "$dest"
>>>                 cp -fpPR "$src"/* "$dest"
>>> +               # Get hidden files as well, but carefully
>>> +               for i in "$src"/.*
>>> +               do
>>> +                       if [ "$i" != "$src"/. -a "$i" != "$src"/.. ];
>> then
>>> +                              cp -fpPR "$i" "$dest"
>>> +                       fi
>>> +               done
>>>         fi
>>>  }
>>>
>>> If anyone has a better way to address the copy operations above, that
>>> would be great.
>>
>> So, I said this on IRC, but more formally, how about just for i in
>> "$src"/.??* do as this lets us know we don't have '.' or '..', and if we
>> skip out on '.a' or something being installed, that reeks of a bug in
>> the program in question that should be fixed anyways (and would
>> catch .config and others).
> 
> 
> Alternatively, could for i in "$src".[a-zA-Z]*, I doubt we care about
> dotfiles starting with a number.

rm_work needs a similar fix. In webkit gtk we set S to WORKDIR and
rm_work skips the 2 gigabyte .libs directory.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFL2S+6MkyGM64RGpERAgmlAJ4yDKxJ/JDNf71meEOkVK+iUHPXpQCgt1ex
U3fzV/UiLdmSYklkcU1seMw=
=bpD4
-----END PGP SIGNATURE-----




      reply	other threads:[~2010-04-29  7:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 16:24 Fix: stage hidden files as well Mike Westerhof
2010-04-28 21:49 ` Tom Rini
2010-04-28 23:52   ` Chris Larson
2010-04-29  7:05     ` Koen Kooi [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='hrbb3r$dkf$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@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