From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yann E. MORIN Date: Thu, 28 Jan 2016 19:15:11 +0100 Subject: [Buildroot] [PATCH 13/16 v3] core/legal-info: also save extra downloads In-Reply-To: References: Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Some packages, like perl, download extra files that end up as part of the source that Buildroot builds. Up until now, those files were not saved in the legal-info output. Add those files to the legal-info output. The unfortunate side-effect is that we will also save the secondary archive for the external blackfin toolchains; however, we already do save the binary release of some external toolchains when they do not provide actual source archives. This is inherently bad, as those are not source archives, but solving this is a bigger concern, for another series... Signed-off-by: "Yann E. MORIN" Cc: Luca Ceresoli Cc: Thomas Petazzoni Reviewed-by: Luca Ceresoli --- Changes v2 -> v3: - typo (Luca) - incorporate the post-commit log message (the part about the side-effect) into the commit log itself, it makes sense to not forget about that --- package/pkg-generic.mk | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/package/pkg-generic.mk b/package/pkg-generic.mk index f6132b3..b59af9e 100644 --- a/package/pkg-generic.mk +++ b/package/pkg-generic.mk @@ -820,10 +820,12 @@ else # Other packages ifeq ($$($(2)_REDISTRIBUTE),YES) -# Copy the source tarball - $$(Q)$$(call hardlink-copy,\ - $$(DL_DIR)/$$($(2)_ACTUAL_SOURCE_TARBALL),\ - $$($(2)_REDIST_SOURCES_DIR)) +# Copy the source tarball and any extra downloads, but not +# patches, as they are handled specially afterwards. + $$(foreach e,$$($(2)_ACTUAL_SOURCE_TARBALL) $$(notdir $$($(2)_EXTRA_DOWNLOADS)),\ + $$(Q)$$(call hardlink-copy,\ + $$(DL_DIR)/$$(e),\ + $$($(2)_REDIST_SOURCES_DIR))$$(sep)) # Copy patches and generate the series file # Because patches may come from various places (bundled in Buildroot, # from one or more global-patch-dir), there might be collisions on the -- 1.9.1