All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 05/13 v7] core/legal-info: add package version to license directory
Date: Sun, 15 May 2016 11:49:50 +0200	[thread overview]
Message-ID: <20160515094950.GC3877@free.fr> (raw)
In-Reply-To: <c9f705eb-9a8a-176d-6da9-d649d0396a13@mind.be>

Arnout, All,

On 2016-05-14 23:22 +0200, Arnout Vandecappelle spake thusly:
> On 05/13/16 22:11, Yann E. MORIN wrote:
> >Thomas, All,
> >
> >On 2016-05-11 23:43 +0200, Thomas Petazzoni spake thusly:
> >>On Sat, 7 May 2016 22:01:28 +0200, Arnout Vandecappelle wrote:
> >>
> >>>>+	@$$(call legal-warning-pkg,$$($(2)_RAW_BASE_NAME),cannot save license ($(2)_LICENSE_FILES not defined))
> >>>
> >>>  I think this should stay $(2)_RAWNAME, or either it should change as well for
> >>>the legal-warning-source below.
> >>>
> >>>  Other than that:
> >>>Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> >>
> >>I agree with Arnout here (we should keep using $(2)_RAWNAME for the
> >>warning). Yann, what do you think?
> >
> >1. With this patch (and the following one), legal-info now gets saved in
> >   sub-directories named after the paclage name and version, i.e.:
> >
> >    legal-info/licenses/pkg-version/
> >    legal-info/sources/pkg-version/
> >
> >2. With this patch, we also store the package name and version in the
> >   manifest.
> >
> >3. The warnings are stored in the legal-info report.
> >
> >So, I think it is better that the info about packages is the same
> >everywhere: sources/ and licenses/ sub-dirs, entries in the manifest and
> >warnings alike.
> 
>  I completely agree with this reasoning. Note that I wrote:
> 
> >>>   [...] or either it should change as well for
> >>> the legal-warning-source below.

OK, I'll do so. Thanks!

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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-05-15  9:49 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-07 16:14 [Buildroot] [PATCH 00/13 v7] legal-info improvements and completeness (branch yem/legal-4) Yann E. MORIN
2016-05-07 16:14 ` [Buildroot] [PATCH 01/13 v7] support/scripts: add helper to hardlink-or-copy Yann E. MORIN
2016-05-07 18:48   ` Arnout Vandecappelle
2016-05-11 21:23   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 02/13 v7] core/legal-info: use the helper to install source archives Yann E. MORIN
2016-05-07 19:54   ` Arnout Vandecappelle
2016-05-11 21:24   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 03/13 v7] core/pkg-generic: add variable to store the package rawname-version Yann E. MORIN
2016-05-11 21:29   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 04/13 v7] core/legal-info: install source archives in their own sub-dir Yann E. MORIN
2016-05-11 21:40   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 05/13 v7] core/legal-info: add package version to license directory Yann E. MORIN
2016-05-07 20:01   ` Arnout Vandecappelle
2016-05-11 21:43     ` Thomas Petazzoni
2016-05-13 20:11       ` Yann E. MORIN
2016-05-14 21:22         ` Arnout Vandecappelle
2016-05-15  9:49           ` Yann E. MORIN [this message]
2016-05-15 17:50           ` Yann E. MORIN
2016-05-16 21:31             ` Arnout Vandecappelle
2016-06-24 13:50   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 06/13 v7] core/apply-patches: store full path of applied patches Yann E. MORIN
2016-05-07 20:09   ` Arnout Vandecappelle
2016-06-22 20:59     ` Yann E. MORIN
2016-06-24 14:02   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 07/13 v7] support/apply-patches: bail-out on duplicate patch basenames Yann E. MORIN
2016-05-07 20:16   ` Arnout Vandecappelle
2016-06-22 21:01     ` Yann E. MORIN
2016-06-24 14:09   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 08/13 v7] core/legal-info: also save patches Yann E. MORIN
2016-05-07 20:36   ` Arnout Vandecappelle
2016-06-22 21:03     ` Yann E. MORIN
2016-06-24 14:22   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 09/13 v7] core/legal-info: also save extra downloads Yann E. MORIN
2016-05-07 20:42   ` Arnout Vandecappelle
2016-06-24 14:22   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 10/13 v7] legal-info: explicitly state how patches are licensed Yann E. MORIN
2016-06-24 14:25   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 11/13 v7] core/legal-info: generate a hash of all saved files Yann E. MORIN
2016-06-24 15:08   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 12/13 v7] core/pkg-generic: reorder variables definitions for legal-info Yann E. MORIN
2016-06-24 15:10   ` Thomas Petazzoni
2016-05-07 16:14 ` [Buildroot] [PATCH 13/13 v7] core/legal-info: ensure legal-info works in off-line mode Yann E. MORIN
2016-06-24 15:11   ` Thomas Petazzoni
2016-06-22 21:12 ` [Buildroot] [PATCH 00/13 v7] legal-info improvements and completeness (branch yem/legal-4) Yann E. MORIN
2016-06-24 15:11 ` Thomas Petazzoni
2016-06-24 17:20   ` Yann E. MORIN

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=20160515094950.GC3877@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 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.