From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dan.rpsys.net ([93.97.175.187]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1UeLph-0003Pg-Dl for bitbake-devel@lists.openembedded.org; Mon, 20 May 2013 10:52:56 +0200 Received: from localhost (dan.rpsys.net [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id r4K8bZpE022937; Mon, 20 May 2013 09:37:35 +0100 X-Virus-Scanned: Debian amavisd-new at dan.rpsys.net Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id TA2uQs1TZ4td; Mon, 20 May 2013 09:37:34 +0100 (BST) Received: from [192.168.3.10] (rpvlan0 [192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id r4K8bRNK022922 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 20 May 2013 09:37:28 +0100 Message-ID: <1369038832.1619.3.camel@ted> From: Richard Purdie To: Martin Jansa Date: Mon, 20 May 2013 09:33:52 +0100 In-Reply-To: <20130519123255.GG3196@jama> References: <1368958915.32727.96.camel@ted> <20130519123255.GG3196@jama> X-Mailer: Evolution 3.6.2-0ubuntu0.1 Mime-Version: 1.0 Cc: "Ashfield, Bruce" , "Hart, Darren" , Koen Kooi , bitbake-devel Subject: Re: [PATCH] fetch2: Shorten long srcrevs X-BeenThere: bitbake-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 May 2013 08:52:58 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Sun, 2013-05-19 at 14:32 +0200, Martin Jansa wrote: > On Sun, May 19, 2013 at 01:21:55PM +0300, Richard Purdie wrote: > > The long srcrevs are mainly used or the workdir construction as well as > > the package version. The long entries are hashes generated by the git fetcher > > and other scms using a similar revision mechanism. > > > > We need these to change when the package changes however collisions are > > unlikely to happen within the domains we care about. The long revisions > > have generated negative user feedback due to the use in path and file > > names. > > > > This patch therefore truncates the revisions to 10 characters maximum. > > What about 7 characters like git log --oneline is using? git uses varying lengths depending on whether it detects collisions. I really don't want to have to do the collision detection or worry about this so 10 characters seemed like a nice number, its short enough to address the complaints but long enough to avoid problems. > SRCREVs in recipes are still supposed to be 40 characters for git, > right? Because otherwise this part needs to be changed too: > > lib/bb/fetch2/git.py > # Ensure anything that doesn't look like a sha256 > # checksum/revision is translated into one > if not ud.revisions[name] or len(ud.revisions[name]) != 40 or (False in [c in "abcdef0123456789" for c in ud.revisions[name]]): Correct, we still specify the exact revisions, this just truncates it when its used in the user visible places like the version in the directory name or package version. Cheers, Richard