[Buildroot] Is it possible to override a package version from BR2_EXTERNAL?

[Buildroot] Is it possible to override a package version from BR2_EXTERNAL?

[Patrick Doyle]

I am asking because it appears (for the moment) that the 2016.01
host-uboot-tools mkenvimage utility does not generate an environment
file compatible with my non-2016.01 u-boot.

I will try changing UBOOT_TOOLS_VERSION to 2015.01 in uboot-tools.mk,
but that is not a long term solution -- I would rather use a pristine
buildroot source tree with by BR2_EXTERNAL customizations for kernel
_defconfig files & the like.

Or, it's possible that something else entirely is wrong with my
environment file and it has nothing to do with mkenvimage.  But I am
still curious about overriding specific package revisions on a
case-by-case basis.

--wpd

[Buildroot] Is it possible to override a package version from BR2_EXTERNAL?

[Arnout Vandecappelle]

On 02/26/16 16:03, Patrick Doyle wrote:
> I am asking because it appears (for the moment) that the 2016.01
> host-uboot-tools mkenvimage utility does not generate an environment
> file compatible with my non-2016.01 u-boot.

 That is weird... As far as I know, mkenvimage should stay backward-compatible.
Unless, of course, your u-boot has some hacks that make it incompatible with
upstream u-boot...


> 
> I will try changing UBOOT_TOOLS_VERSION to 2015.01 in uboot-tools.mk,
> but that is not a long term solution -- I would rather use a pristine
> buildroot source tree with by BR2_EXTERNAL customizations for kernel
> _defconfig files & the like.
> 
> Or, it's possible that something else entirely is wrong with my
> environment file and it has nothing to do with mkenvimage.  But I am
> still curious about overriding specific package revisions on a
> case-by-case basis.

 Nope, that's not possible. It's been discussed a couple of times on the list,
search the archives for details. In short, because of the order in which make
evaluates things, by the time you get to the BR2_EXTERNAL customisations it's
too late.

 It's also not possible to override the version in the override file, because
then the package file will just override your assignment.

 What you _can_ do, is to get a local copy and use UBOOT_TOOLS_OVERRIDE_SRCDIR.
But that's also not a long-term solution.

 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:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] Is it possible to override a package version from BR2_EXTERNAL?

[Patrick Doyle]

On Fri, Feb 26, 2016 at 3:14 PM, Arnout Vandecappelle <arnout@mind.be> wrote:
> On 02/26/16 16:03, Patrick Doyle wrote:
>> I am asking because it appears (for the moment) that the 2016.01
>> host-uboot-tools mkenvimage utility does not generate an environment
>> file compatible with my non-2016.01 u-boot.
>
>  That is weird... As far as I know, mkenvimage should stay backward-compatible.
> Unless, of course, your u-boot has some hacks that make it incompatible with
> upstream u-boot...
And, in fact, mkenvimage was fine... I just took careful aim at my
foot and fired my gun :-)

But I was still curious about how to override the version installed
for a single package.  Now I know the answer is "You can't do that
easily."

OK, thanks.

--wpd