From: Jason Wessel <jason.wessel@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Robert Yang <liezhi.yang@windriver.com>,
<bitbake-devel@lists.openembedded.org>,
Mark Hatle <mark.hatle@windriver.com>
Subject: Re: [PATCH 1/1] fetch2: remove "." in the end
Date: Mon, 27 Jun 2016 08:46:25 -0500 [thread overview]
Message-ID: <57712E31.6000100@windriver.com> (raw)
In-Reply-To: <1466774122.3319.235.camel@linuxfoundation.org>
On 06/24/2016 08:15 AM, Richard Purdie wrote:
> On Fri, 2016-06-24 at 00:55 -0700, Robert Yang wrote:
>> From: Jason Wessel <jason.wessel@windriver.com>
>>
>> The filename can't be "foo." for MS Windows filesystem, it will
>> renamed
>> to "foo" automatically, so we can't upload sources like "foo." to the
>> Windows server, remove "." in the end will fix the problem.
> This patch on its own is probably ok. What I worry about is that if I
> merge this, I'll then get all the follow ups which for example force
> lower or upper case everywhere, remove ":" characters from all
> filenames (including sstate?), remove various other characters and so
> on.
>
> We don't run on windows filesystems and we're not likely ever to be
> able to.
>
> So what are we aiming for here?
It is compatibility with browsing and copying the bitbake/oe directory structures + the download cache. We certainly don't expect to be building directly on Windows with a native bitbake. Today however, you can directly use git on Windows and building with the cross API's from a generated SDK.
Cheers,
Jason.
next prev parent reply other threads:[~2016-06-27 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 7:55 [PATCH 0/1] fetch2: remove "." in the end Robert Yang
2016-06-24 7:55 ` [PATCH 1/1] " Robert Yang
2016-06-24 13:15 ` Richard Purdie
2016-06-27 3:31 ` Robert Yang
2016-06-27 13:46 ` Jason Wessel [this message]
2016-06-27 13:51 ` Richard Purdie
2016-06-27 14:37 ` Jason Wessel
2016-06-27 18:19 ` Mark Hatle
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=57712E31.6000100@windriver.com \
--to=jason.wessel@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=liezhi.yang@windriver.com \
--cc=mark.hatle@windriver.com \
--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.