Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>,
	Robert Yang <liezhi.yang@windriver.com>,
	bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: Filename too long
Date: Thu, 19 Jan 2017 16:05:18 +0000	[thread overview]
Message-ID: <1484841918.4367.426.camel@linuxfoundation.org> (raw)
In-Reply-To: <8d3f903a-0ff2-8c27-e2bc-258ad2c7fd7d@windriver.com>

On Thu, 2017-01-19 at 09:07 -0600, Mark Hatle wrote:
> On 1/19/17 4:21 AM, Richard Purdie wrote:
> > 
> > On Thu, 2017-01-19 at 14:13 +0800, Robert Yang wrote:
> > > 
> > Looking at the code in your patch, this second piece clearly isn't
> > true
> > due to this code:
> > 
> >           if gitsrcname.startswith('.'):
> >               gitsrcname = gitsrcname[1:]
> > 
> > I also don't believe this patch is correct since we're meant to be
> > creating a filename, not a path and if you leave the '/' characters
> > in,
> > it isn't a filename. I think we likely just need to truncate the
> > path
> > to the last say 225 chars if its over length. The unique piece
> > should
> > be towards the right hand end of the name.
> Ok.. I can certainly implement that.  Should the truncation be in the
> lockfile code or in the code that generatd the name itself?

Gut feeling says I think the generated name is safest.

Cheers,

Richard


      reply	other threads:[~2017-01-19 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 19:02 Filename too long Mark Hatle
2017-01-19  6:13 ` Robert Yang
2017-01-19 10:21   ` Richard Purdie
2017-01-19 15:07     ` Mark Hatle
2017-01-19 16:05       ` Richard Purdie [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=1484841918.4367.426.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=liezhi.yang@windriver.com \
    --cc=mark.hatle@windriver.com \
    /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