From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] openssl: remove patch's git-hash to support fat/ntfs systems
Date: Fri, 30 Oct 2015 17:59:42 +0100 [thread overview]
Message-ID: <5633A1FE.3030906@mind.be> (raw)
In-Reply-To: <CALe+oY-tjfi_UmiL6kS6FmSbX2TiQhFW=E6yKjs+aXYyFuO21Q@mail.gmail.com>
On 30-10-15 17:57, James Knight wrote:
> Arnout,
>
> On Fri, Oct 30, 2015 at 12:42 PM, Arnout Vandecappelle <arnout@mind.be> wrote:
>> I think that one trumps supporting FAT or NTFS as your DL_DIR filesystem, so
>> that's a NACK from me.
>
> Agreed.
>
> I'll try to find a way to work around the setup I have then, maybe try
> a sanitation method (like you've suggested).
The sanitation is an infrastructural change, of course. I would start with
replacing all the uses of <pkg>_SOURCE with a newly introduced <pkg>_DL_SOURCE
(which also includes the DL_DIR). Then in a second step you can sanitize
_DL_SOURCE and update the download infra.
Regards,
Arnout
> I'll mark the patch as
> rejected. I'd be curious if anyone else has any other comments on
> this.
>
--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-10-30 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 15:27 [Buildroot] [PATCH 1/1] openssl: remove patch's git-hash to support fat/ntfs systems James Knight
2015-10-30 16:42 ` Arnout Vandecappelle
2015-10-30 16:57 ` James Knight
2015-10-30 16:59 ` Arnout Vandecappelle [this message]
2015-10-31 8:43 ` Peter Korsgaard
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=5633A1FE.3030906@mind.be \
--to=arnout@mind.be \
--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