The amausement stays on my side - because the name of the bb file is not causing package dependency problems:
DMM control file of a secondstage package on the dm7020hd
Package: dreambox-secondstage
Version: 89-r12.0
Description: Dreambox second stage bootloader
Dreambox second stage bootloader
Section: base
Priority: required
Maintainer: OE-Core Developers <openembedded-core@lists.openembedded.org>
License: CLOSED
Architecture: dm7020hd
Your control file from PLi feed:
Package: dreambox-secondstage-dm7020hd
Version: 89-r20.0
Description: Dreambox second stage bootloader
Dreambox second stage bootloader.
Section: base
Priority: required
Maintainer: OE-Core Developers <openembedded-core@lists.openembedded.org>
License: CLOSED
Architecture: dm7020hd
OE: dreambox-secondstage-dm7020hd
Depends: mtd-utils
Source: http://sources.dream...age-dm7020hd-89.
So you decided to put the boxname in the Package name instead of using the Architecture as it should be.
Wich means everybody putting only secondstage-dreambox in his Depends has .... a problem and now has to build boxspecific packages or remove the Depends ?
Which means also great thingsl ike that:
opkg update
opkg download dreambox-secondstage-dm7020hd
Downloading http://downloads.pli....0_dm7020hd.ipk.
wget: server returned error: HTTP/1.1 404 Not Found
Collected errors:
* opkg_download: Failed to download http://downloads.pli...ox-secondstage-dm7020hd_89-r20.0_dm7020hd.ipk
But better you all get your sleep
PS: There is no real difference in a backup for Dreamboxes or the other boxes, instead that you use the buildimage binary at the end to make a single nfi file out of it or a tar command to create a single tar.xz file. Which is very similar to the ZIP files the other boxmakers are using. But I'm not blaming anybody for not supporting some boxes - as I do the same - just my list is longer
gutemine
Edited by gutemine, 17 July 2016 - 23:21.