From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/golang: new package
Date: Thu, 30 Jul 2015 18:31:55 +0200 [thread overview]
Message-ID: <20150730163154.GA3744@free.fr> (raw)
In-Reply-To: <CA+h8R2pvaeQ4K7szq+Dr7dYT1cjGTW3QhB4jRNhKj6NY7P289w@mail.gmail.com>
Christian, all,
On 2015-07-29 22:28 +0000, Christian Stewart spake thusly:
> > We're not doing this for any other package, so why should we be doing
> > this for golang?
> >
>
> Because it's very critical that Go have the exact same src, include, and
> pkg tree in that location. If we don't ensure any previous files have been
> cleared out it WILL cause major problems down the line.
But Thomas is right: we're not doing it for other packages, even if they
have the same requirements.
In fact, Buildroot only guarantees everything is perfect when building
from scratch. Any cycle of build-modify-build has never been guaranteed
to produce the same results as just the last build alone would give.
So, I concur with Thomas: we need not ensre cleanliness, and should
assume that directory is clean. Hence there's no reason to remove it
beforehand.
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. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2015-07-30 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 20:35 [Buildroot] [PATCH] package/golang: new package Yann E. MORIN
2015-07-29 21:12 ` Thomas Petazzoni
2015-07-29 21:20 ` Yann E. MORIN
2015-07-29 21:37 ` Thomas Petazzoni
2015-07-29 22:28 ` Christian Stewart
2015-07-30 16:31 ` Yann E. MORIN [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=20150730163154.GA3744@free.fr \
--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