All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Bugs cleanup (input requested)
Date: Mon, 10 Feb 2014 21:39:03 +0100	[thread overview]
Message-ID: <52F938E7.8010101@mind.be> (raw)
In-Reply-To: <20140210154305.0db0bb01@skate>

On 02/10/14 15:43, Thomas Petazzoni wrote:
> Dear Thomas De Schampheleire,
> 
> On Mon, 10 Feb 2014 11:21:24 +0100, Thomas De Schampheleire wrote:
> 
[snip]
>> https://bugs.busybox.net/show_bug.cgi?id=4339
>> Allow override of DL_DIR in extract step
>>
>> I have requested the author of the problem for additional info, which
>> was provided. They are using a custom dl dir for company packages, by
>> adding the following in these packages' .mk file:
>> $($(PKG)_BUILD_DIR)/.stamp_% : DL_DIR=$(OUR_SPECIAL_DL_DIR)
>> In order to make this work, they need the following change in
>> package/pkg-generic.mk:
>>
>>   # default extract command
>>   $(2)_EXTRACT_CMDS ?= \
>> -     $$(if $$($(2)_SOURCE),$$(INFLATE$$(suffix $$($(2)_SOURCE)))
>> $(DL_DIR)/$$($(2)_SOURCE) | \
>> +     $$(if $$($(2)_SOURCE),$$(INFLATE$$(suffix $$($(2)_SOURCE)))
>> $$(DL_DIR)/$$($(2)_SOURCE) | \
>>       $(TAR) $(TAR_STRIP_COMPONENTS)=1 -C $$($(2)_DIR) $(TAR_OPTIONS) -)
>>
>>   # post-steps hooks
>>
>> Although the usage is pretty funky, the patch is not very invasive and
>> I don't have a strong objection.  But I could understand that other
>> people don't like this. I think there are three alternatives:
>> - accept the patch
>> - reject the patch
>> - reject the patch but propose another solution
> 
> Reject the patch, with the following explanations:
> 
>  * The "file" site method can be used to "download" tarballs from a
>    local directory, when needed.
> 
>  * The licensing infrastructure allows to create a directory with all
>    the open-source tarballs, keeping them separate from proprietary
>    bits, for delivery to customers.
> 
> I would also add that supporting highly-specific use cases in the
> package infrastructure is not a good idea, because we might very easily
> break them in the future if they are too specific and therefore not
> used by enough people to be tested when we make changes.

 It is true that their use case should be solved with the legal-info
infrastructure - and if that doesn't work for them, it should be fixed there.

 However, the patch is still valid for a different reason: it makes
things more consistent. We use $$ almost everywhere within
generic-package, so ideally it should be done there as well.


 Regards,
 Arnout


> 
> Best regards,
> 
> Thomas
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2014-02-10 20:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 10:21 [Buildroot] Bugs cleanup (input requested) Thomas De Schampheleire
2014-02-10 12:02 ` Maxime Hadjinlian
2014-02-10 15:10   ` Thomas De Schampheleire
2014-02-10 14:21 ` Danomi Manchego
2014-02-10 14:43 ` Thomas Petazzoni
2014-02-10 15:12   ` Thomas De Schampheleire
2014-02-10 15:20   ` Thomas De Schampheleire
2014-02-10 16:48     ` Thomas Petazzoni
2014-02-10 17:48       ` Thomas De Schampheleire
2014-02-10 17:53         ` Thomas Petazzoni
2014-02-10 20:39   ` Arnout Vandecappelle [this message]
2014-02-11 20:52     ` Thomas De Schampheleire

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=52F938E7.8010101@mind.be \
    --to=arnout@mind.be \
    --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.