On Mon, May 28, 2012 at 12:44 PM, Phil Blundell <[email protected]> wrote:
> On Sun, 2012-05-13 at 16:28 +0300, Leonid Borisenko wrote:
>> Custom metadata field with supported firmware version(s) could be
>> included into package control file for preventing of installing packaged
>> modifications onto unsupported firmware.
>
> Why isn't RDEPENDS sufficient for this?

I didn't think about using RDEPENDS for specifing supported firmware version.

I'll try to discuss possible scenario with RDEPENDS. Correct me please
if I'll miss your point.

So RDEPENDS transforms into Depends field in package control file (I'm
speaking about ipk/deb, as it's the chosen format). Depends field
contains list of packages (with their's versions) on which target
package is depended. Dependencies must be installed before target
package and target package will not be installed if all dependencies
will not be satisfied.

So there could be empty package kindle-touch-firmware on which target
package will depend. Supported version of firmware could be specified
as version of package. Package will be empty as only it's version
string is signifcant.

Using of stub package for describing supported version of stock
proprietary firmware is pretty weird (as for me), but on the other
side it's OK as it uses existing capabilities of package format and
existing support of package format in OE.

However, user-defined metadata fields are existing capabilities of
deb/ipk format too [1].

Also, it could be reasonable to override supported firmware
specification and install package forcefully. Noone could foresee
whether his/her package will work on future firmware version, but it
could in fact work. If package is abandoned and supported firmware
version wasn't changed in long time and user want to install it on
newer firmware, then using of stub package in Depends field will bring
problems. It's not possible to ignore just one package from Depends
field, all packages from Depends field will be ignored.

[1] http://www.debian.org/doc/debian-policy/ch-controlfields.html#s5.7

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to