[Buildroot] Overriding Buildroot packages

[Arnout Vandecappelle <arnout@mind.be>]

On 25-11-15 10:48, Hajime Branko Yamasaki Vukelic wrote:
> On Tue, Nov 24, 2015 at 11:30 PM, Arnout Vandecappelle <arnout@mind.be> wrote:
> 
> [SNIP]
> 
>>> Ideally, ability to override some aspect of an existing package (e.g.,
>>> only its version, or only the source URL, or something along those
>>> lines) would be great to have. If not, then, a mechanism to make two
>>> packages equivalent (something like virtual packages but applicaable
>>> to packages that are not explicitly virtual) would also work (e.g.,
>>> `POSTGRES_95_PROVIDES = postgres`, that causes having postgres-95
>>> selected to satisfy dependency requirement for a package that
>>> selects/depends on postgres).
>>
>>  There is a fairly easy way to make it possible to override the version and
>> dependencies, but I think it's a bit ugly. In inner-generic-package, instead of
>> defining all the rules directly, we could add yet another level of direction and
>> delay the definition of the rules until after BR2_EXTERNAL has been included.
> 
> What if a package has <pkgname>.hash file? If I simply override the
> version, wouldn't that still break when checking the hash?

 That's right, we'd need to find a workaround of that as well.

 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