From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Nicolas Carrier <Nicolas.Carrier@orolia.com>
Cc: "thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] package/pkg-generic.mk: no legal info WARNING if REDISTRIBUTE = NO
Date: Sat, 14 Jan 2023 21:49:23 +0100 [thread overview]
Message-ID: <20230114204923.GD199036@scaer> (raw)
In-Reply-To: <20230114203859.GC199036@scaer>
Nicolas, All,
On 2023-01-14 21:38 +0100, Yann E. MORIN spake thusly:
> On 2023-01-13 13:20 +0000, Nicolas Carrier spake thusly:
[--SNIP--]
> > But in the situation where the packages has explicitly defined
> > FOO_REDISTRIBUTE = NO
> > in its .mk file, it makes no sense since the sources wouldn't be saved
> > anyway.
> Yes, it makes sense.
I now realise that my comment was ambiguoug, given what I was commenting
on. So, let me rephrase:
Indeed, emitting the warning does not make sense. Indeed, what you
explained does make sense.
There, ambiguity resolved. ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-01-14 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 13:20 [Buildroot] package/pkg-generic.mk: no legal info WARNING if REDISTRIBUTE = NO Nicolas Carrier
2023-01-14 20:38 ` Yann E. MORIN
2023-01-14 20:49 ` Yann E. MORIN [this message]
2023-01-16 7:43 ` Nicolas Carrier
2023-01-16 14:46 ` 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=20230114204923.GD199036@scaer \
--to=yann.morin.1998@free.fr \
--cc=Nicolas.Carrier@orolia.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.