Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Some legal-info observations/problems
Date: Thu, 03 Oct 2013 18:50:37 +0200	[thread overview]
Message-ID: <524DA05D.50704@mind.be> (raw)
In-Reply-To: <OF745746BB.02FF7D3A-ON86257BF9.004D84C8-86257BF9.004E01F3@rockwellcollins.com>

On 10/03/13 16:12, Ryan Barnett wrote:
> Danomi, All,
>
> Danomi Manchego <danomimanchego123@gmail.com> wrote on
> 10/03/2013 08:42:55 AM:
>
>> Ryan,
>>
>> On Thu, Oct 3, 2013 at 9:31 AM, Ryan Barnett
>> <rjbarnet@rockwellcollins.com> wrote:
>>>> While I don't need the URL for my process, I currently also don't
> need
>>>> the name of the tarball in manifest.csv (and I leave out this last
>>>> column anyway). So, I'm not opposed to adding this extra column, but
>>>> there may be some caveats: with the OVERRIDE_SRCDIR mechanism it is
>>>> possible for a project to completely change the sources of an
> existing
>>>> package in buildroot. Strictly speaking this could mean that there is
>>>> no relation whatsoever between the URL specified in the .mk file and
>>>> the actual sources used. This is probably very exotic, though, and
>>>> maybe it doesn't really matter for your process.
>>>
>>> You bring up an interesting point that I never thought of. However, in
>>> the application of OVERRIDE_SRCDIR, I would think that it mainly
> intended
>>> for company's application but I could be wrong.

  It was originally intended for temporarily testing a modified version 
of a package, which you commit by generating patches from it. But I 
expect that in companies it will indeed be mainly used for the application.


>> FWIW, several of our projects regularly use permanent OVERRIDE_SRCDIR
>> settings to compile exploded copies of uboot and xloader checked into
>> our source control system, rather than maintain patches against some
>> off-upstream vendor tarball; it's just easier than educating the folks
>> in remote offices about patching.

  Actually, BR2_TARGET_UBOOT_CUSTOM_GIT and 
BR2_TARGET_UBOOT_CUSTOM_TARBALL exist for exactly this purpose. Of 
course, there's no equivalent for xloader, but you should start using 
U-Boot SPL anyway :-)


> Thanks for the use case as I never though of that since I've just maintain
> a large u-boot/x-loader patch set.
>
> My thought for how this column would work is that if the OVERRIDE_SRCDIR
> is used that in the column, "OVERRIDE_SRCDIR Used" would be placed instead
> of the URL. This will also make sure that someone explicitly knows they
> are
> using the OVERRIDE_SRCDIR feature (not that isn't already obvious in
> local.mk)

  Sounds like a good idea to me.

  Regards,
  Arnout

-- 
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

  reply	other threads:[~2013-10-03 16:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 14:06 [Buildroot] Some legal-info observations/problems Thomas De Schampheleire
2013-10-02 14:22 ` Peter Korsgaard
2013-10-02 14:32   ` Thomas De Schampheleire
2013-10-02 15:23 ` Thomas Petazzoni
2013-10-02 16:33   ` Luca Ceresoli
2013-10-03  8:24     ` Thomas De Schampheleire
2013-10-03 16:40       ` Arnout Vandecappelle
2013-10-04  8:54         ` Thomas De Schampheleire
2013-10-04  9:07           ` Thomas Petazzoni
2013-10-04 15:30             ` Ryan Barnett
2013-10-04 15:34               ` Thomas Petazzoni
2013-10-04 15:39                 ` Ryan Barnett
2013-10-04 15:46                 ` Simon Dawson
2013-10-07 22:43                   ` Arnout Vandecappelle
2013-10-09  7:23                     ` Simon Dawson
2013-10-09  7:29                       ` Thomas Petazzoni
2013-10-09  7:31                         ` Simon Dawson
2013-10-05 21:07       ` Luca Ceresoli
2013-10-02 16:31 ` Arnout Vandecappelle
2013-10-03  8:30   ` Thomas De Schampheleire
2013-10-02 18:49 ` Ryan Barnett
2013-10-03  8:34   ` Thomas De Schampheleire
2013-10-03 13:31     ` Ryan Barnett
2013-10-03 13:42       ` Danomi Manchego
2013-10-03 14:12         ` Ryan Barnett
2013-10-03 16:50           ` Arnout Vandecappelle [this message]
2013-10-03 21:38     ` Peter Korsgaard
2013-10-03 22:44       ` Ryan Barnett
2013-10-07  8:19 ` Thomas De Schampheleire
2013-10-09 13:14   ` Luca Ceresoli
2013-10-09 16:46     ` Arnout Vandecappelle
2013-10-11 14:13       ` Thomas De Schampheleire
2013-10-09 19:54     ` Ryan Barnett

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=524DA05D.50704@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox