From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by mail.openembedded.org (Postfix) with ESMTP id E4C4E62132 for ; Mon, 27 Jun 2016 13:46:28 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.15.2/8.15.1) with ESMTPS id u5RDkR6f003979 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Jun 2016 06:46:27 -0700 (PDT) Received: from [192.168.10.15] (172.25.59.217) by ALA-HCA.corp.ad.wrs.com (147.11.189.40) with Microsoft SMTP Server id 14.3.248.2; Mon, 27 Jun 2016 06:46:26 -0700 To: Richard Purdie , Robert Yang , , Mark Hatle References: <1466774122.3319.235.camel@linuxfoundation.org> From: Jason Wessel Message-ID: <57712E31.6000100@windriver.com> Date: Mon, 27 Jun 2016 08:46:25 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <1466774122.3319.235.camel@linuxfoundation.org> Subject: Re: [PATCH 1/1] fetch2: remove "." in the end X-BeenThere: bitbake-devel@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussion that advance bitbake development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 13:46:29 -0000 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit 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 >> >> 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.