[LEDE-DEV] Using Conflicts:

[Philip Prindeville]

> On Mar 9, 2017, at 3:25 AM, Jo-Philipp Wich <jo at mein.io> wrote:
> 
> Hi,
> 
>> Is there a reason we don’t use Conflicts: information from the
>> packaging to stop overlapping installs from being selected when doing
>> a build?
> 
> yes. The buildroot uses Kconfig logic, while Conflicts: is an opkg concept.
> 
>> I understand that the buildbots build everything…  but it should be
>> possible to differentiate between ’y’ and ‘m’ and detect to packages
>> providing the same paths as both being combined into the same
>> image/ISO (for example, below, /sbin/insmod being provided by “kmod”
>> and “ubox” both)?
>> 
>> Right?  Or am I missing something?
> 
> The problem is that packages like busybox or ubox provide more
> functionality than just the conflicting applets. The proper approach
> would be something like alternatives; Yousong sent an rfc series for
> that recently.
> 
> ~ Jo


Yeah, it strikes me also that we don’t have a way of explicitly calling out what a package builds as part of the meta-description: instead we have to build it and then see what the bill-of-materials is for the generated .pkg file.

-Philip