All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Søren Holm" <sgh@sgh.dk>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Trouble packaging files containing space
Date: Mon, 28 Oct 2013 18:14:56 +0100	[thread overview]
Message-ID: <2173657.67B60vOxq4@koontz> (raw)
In-Reply-To: <5221494.eWKnjLPuZO@helios>

Mandag den 28. oktober 2013 16:17:46 skrev Paul Eggleton:
> On Monday 28 October 2013 17:05:54 Søren Holm wrote:
> > Mandag den 28. oktober 2013 16:01:24 skrev Paul Eggleton:
> > > Søren, are you getting unpackaged file warnings? Are the files listed if
> > > you look under image/ in the work directory for the recipe? FWIW, I just
> > > tested here and installing files whose filenames contain spaces worked
> > > just fine.
> > 
> > I get erro regarding files installed but not shipped - but that's a
> > differen issue I think. That particular issue is strange sine the
> > un-shupped files are source-files that I do not install. They end up in
> > image/ during do_package.
> > 
> > The image-dir contains all the files including the files containing
> > spaces.
> 
> I think I might need some more details - can you please paste the actual
> error, the relevant parts of the recipe and a directory listing under
> image/${prefix}/local ?

Having a recipe containing just this works. I'll try stripping my original 
much larger recipe to see what breaks it.


do_install() {
        touch "${D}/file with spaces.txt"
}

FILES_${PN} = "/"



-- 
Søren Holm


      reply	other threads:[~2013-10-28 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28  6:26 Trouble packaging files containing space Søren Holm
2013-10-28 14:55 ` Gary Thomas
2013-10-28 16:01   ` Paul Eggleton
2013-10-28 16:05     ` Søren Holm
2013-10-28 16:17       ` Paul Eggleton
2013-10-28 17:14         ` Søren Holm [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=2173657.67B60vOxq4@koontz \
    --to=sgh@sgh.dk \
    --cc=paul.eggleton@linux.intel.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.