From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Per-package download folders and Git caching
Date: Tue, 3 Apr 2018 18:23:24 +0200 [thread overview]
Message-ID: <20180403162324.GB2335@scaer> (raw)
In-Reply-To: <876058qvi4.fsf@dell.be.48ers.dk>
Peter, Arnout, All,
On 2018-04-03 15:17 +0200, Peter Korsgaard spake thusly:
> >>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> > 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'.
Should we do a cp if ln fails, then?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-04-03 16:23 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 [this message]
2018-04-03 16:49 ` Peter Korsgaard
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=20180403162324.GB2335@scaer \
--to=yann.morin.1998@free.fr \
--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