From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork cleanup week #24
Date: Thu, 16 Jun 2016 19:30:16 +0200 [thread overview]
Message-ID: <20160616173016.GD3665@free.fr> (raw)
In-Reply-To: <20160616115627.6760c0dd@free-electrons.com>
Thomas?, All,
On 2016-06-16 11:56 +0200, Thomas Petazzoni spake thusly:
> On Thu, 16 Jun 2016 11:52:29 +0200, Thomas De Schampheleire wrote:
> > > I am not sure what is the best solution between:
> > >
> > > - Defining <foo>_SITE to undefined when no value is specified by the
> > > package (which is your proposal)
> > >
> > > - Do not add to <pkg>_ALL_DOWNLOADS the files for which there is
> > > no :// in the URL, and <pkg>_SITE is empty. This was the proposal
> > > made by Yann in
> > > http://lists.busybox.net/pipermail/buildroot/2016-February/153999.html.
> >
> > This does not give the intended result. It was in the thread but in
> > March, so mailman fails to link it (meh...)
> > http://lists.busybox.net/pipermail/buildroot/2016-March/156416.html
>
> Ah, yes. Stupid mailman.
>
> In any case, for such situations, it is good if a new patch gets sent,
> which summarizes the problem, the different approaches, and why the
> proposed approach was chosen.
>
> It is really hard to remember all the details of this discussion that
> happened months ago.
>
> > > - Error out when both <pkg>_SITE is empty and <pkg>_SOURCE is
> > > non-empty.
> >
> > I guess this could also work. If you prefer this I can cook up a real patch.
> > Input from others is welcome too, of course.
>
> Let's wait a bit for others to speak up.
Well, I prefer Thomas P. proposal: bail out if <pkg>_SITE is empty and
<pkg>_SOURCE is not.
> What I find a bit with with the "undefined" idea, is that people will
> get download failure due to http://undefined/foo not being available.
> To me, it seems to make more sense to error out when _SITE is empty, we
> will provide an even clearer error than a weird download failure on
> http://undefined/foo.
Yes, this is definitely not user-friendly. Maybe:
http://you-forgot-to-set-<pkg>_SITE/pkg-version-blabla
Just kidding. ;-]
Regards,
Yann E. MORIN.
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
--
.-----------------.--------------------.------------------.--------------------.
| 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:[~2016-06-16 17:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 20:06 [Buildroot] Patchwork cleanup week #24 Thomas Petazzoni
[not found] ` <CAJsd3zJkzAUJhvBPJ9hdQ60YmjSjuB7sahptmLFx6-1V70fLAg@mail.gmail.com>
2016-06-15 21:18 ` Thomas Petazzoni
2016-06-16 7:18 ` Thomas De Schampheleire
2016-06-16 7:32 ` Thomas Petazzoni
2016-06-16 9:52 ` Thomas De Schampheleire
2016-06-16 9:56 ` Thomas Petazzoni
2016-06-16 17:30 ` Yann E. MORIN [this message]
2016-06-16 17:23 ` Yann E. MORIN
2016-06-18 20:56 ` Thomas Petazzoni
2016-06-18 14:14 ` Romain Naour
[not found] ` <4209f432-0fbd-8d44-7194-c99829f66e2e@smile.fr>
2016-06-22 5:45 ` Alexey Brodkin
2016-06-24 7:24 ` Vlad Zakharov
2016-06-24 7:32 ` Thomas Petazzoni
2016-06-24 9:13 ` Alexey Brodkin
2016-06-24 9:15 ` Thomas Petazzoni
2016-06-24 9:17 ` Alexey Brodkin
2016-07-01 7:59 ` Romain Naour
2016-06-22 6:14 ` Cam Hutchison
2016-06-30 23:51 ` Cam Hutchison
2016-07-01 7:01 ` Thomas Petazzoni
2016-06-22 20:57 ` Arnout Vandecappelle
2016-06-26 11:07 ` Jörg Krause
2016-06-26 12:53 ` Thomas Petazzoni
2016-07-24 20:23 ` Thomas Petazzoni
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=20160616173016.GD3665@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