Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Per-package download folders and Git caching
Date: Tue, 03 Apr 2018 18:49:42 +0200	[thread overview]
Message-ID: <87k1top74p.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180403162324.GB2335@scaer> (Yann E. MORIN's message of "Tue, 3 Apr 2018 18:23:24 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

Hi,

>> >  I know a few users that put their download directory on a samba share or a
 >> > virtualbox/vmware share which has NTFS as underlying filesystem. Although NTFS
 >> > does support hardlinks, I'm not sure that Samba and virtualbox/vmware do. Any
 >> > idea what will happen in such a case?
 >> 
 >> Then presumably the ln call will fail and we download the tarball again
 >> in the new location?

 > No, the script would fail, because the script runs with 'set -e'.

Ahh yes :/

 > Should we do a cp if ln fails, then?

That sounds like a sensible fallback, yes.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-04-03 16:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03 12:17 [Buildroot] Per-package download folders and Git caching Thomas Petazzoni
2018-04-03 12:55 ` Arnout Vandecappelle
2018-04-03 13:17   ` Peter Korsgaard
2018-04-03 16:23     ` Yann E. MORIN
2018-04-03 16:49       ` Peter Korsgaard [this message]
2018-04-03 17:49         ` Yann E. MORIN
2018-04-03 18:10           ` Peter Korsgaard
2018-04-03 20:44           ` Arnout Vandecappelle
2018-04-03 20:48             ` Yann E. MORIN
2018-04-04 22:28               ` Arnout Vandecappelle

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=87k1top74p.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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