Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/6] package/qt5: prepare for per-version hash files
Date: Sat, 13 Oct 2018 09:07:22 +0200	[thread overview]
Message-ID: <20181013070722.GE31509@scaer> (raw)
In-Reply-To: <49cfb8fd-924b-f1e9-8524-3aae0055f4e9@lucaceresoli.net>

Luca, All,

On 2018-10-13 00:07 +0200, Luca Ceresoli spake thusly:
> On 12/10/2018 17:46, Yann E. MORIN wrote:
> > On 2018-10-12 09:12 +0200, Luca Ceresoli spake thusly:
> >> On 07/10/2018 13:57, Yann E. MORIN wrote:
[--SNIP--]
> >>> -# Hashes for license files:
> >>> -sha256 d2cfc059acb4abd8e513cd0a73cd8489f34cbafa7bc34d5d31fb3210821cf8ca LICENSE.GPLv3
> >>> -sha256 9e63a04ce021b8bf811b30881fa51c8c3db88afeead942cd59322f2fb69c75bc LICENSE.LGPLv3
> >>> -sha256 ed8742a95cb9db653a09b050e27ccff5e67ba69c14aa2c3137f2a4e1892f6c0d LICENSE.FDL
> >>
> >> Shouldn't this removal happen in patch 5?
> > 
> > Notice how we create the .hash file for the 5.11.2 version? This means
> > that the hash-check for license files will be using it rather than the
> > main hash file.
> > 
> > So, the hashes for the license of the 5.11.2 version are no longer
> > usefull in the main hash file, ergo they get removed.
> 
> So this is a bit different from what you do to qt5base and
> qt5virtualkeyboard. For those you leave the license hashes both in the
> versioned files and the unversioned files.

Ah, right, I forgot to do it for those, indeed. I've fixed it.

> However this difference has no practical effect since after patch 3
> there are versioned hashes for all versions, thus the unversioned file
> is ignored. Patch 5 will trim all the unused lines anyway, so I'm OK if
> this is committed as-is.

In fact, I'd prefer to respin with:

  - a patch that does things consistently, i.e. that either removes the
    license for the two paclages, or for none of them, not tsomething
    in-between ;

  - a better commit log that adds the explanations you requested.

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:[~2018-10-13  7:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-07 11:57 [Buildroot] [PATCH 0/6] core: look for package's hashes in versioned sub-directory Yann E. MORIN
2018-10-07 11:57 ` [Buildroot] [PATCH 1/6] core: add a variable that points to the package's hash file Yann E. MORIN
2018-10-12  7:43   ` Luca Ceresoli
2018-10-07 11:57 ` [Buildroot] [PATCH 2/6] legal-info: use the per-package variable to get the " Yann E. MORIN
2018-10-12  7:43   ` Luca Ceresoli
2018-10-07 11:57 ` [Buildroot] [PATCH 3/6] package/qt5: prepare for per-version hash files Yann E. MORIN
2018-10-12  7:12   ` Luca Ceresoli
2018-10-12 15:46     ` Yann E. MORIN
2018-10-12 22:07       ` Luca Ceresoli
2018-10-13  7:07         ` Yann E. MORIN [this message]
2018-10-07 11:57 ` [Buildroot] [PATCH 4/6] core/download: do not hard-code the path to hte package hash file Yann E. MORIN
2018-10-12  7:45   ` Luca Ceresoli
2018-10-07 11:57 ` [Buildroot] [PATCH 5/6] package/qt5: drop unversioned hash files Yann E. MORIN
2018-10-07 11:57 ` [Buildroot] [PATCH 6/6] docs/manual: document location of hash files for multi-versions packages Yann E. MORIN
2018-10-12  7:45   ` Luca Ceresoli
2018-10-11  8:19 ` [Buildroot] [PATCH 0/6] core: look for package's hashes in versioned sub-directory 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=20181013070722.GE31509@scaer \
    --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