Do you think it is possible to supply for your current release the thing called "ImageBuilder"?
With this kind of prepared images, the installation of LibraryBox/PirateBox becomes more a "wait until it is done" scenario over hacking stuff in the command line.
edit: What the hell is ImageBuilder? http://wiki.openwrt.org/doc/howto/obtain.firmware.generate ; A Elegant way to refit the stock binary firmwares with other software then install without recompiling everything.
What do you think?
The text was updated successfully, but these errors were encountered:
Yes, this is the limitation of the imagebuilder, but to be honest - I used the 32bit openwrt-imagebuilder on my 64bit machine without issues for one year.
As the OpenWrt-Yun compile worked only on my 32bit-Debian VM inside my 64Bit machine, I don't think that is a really problematic situation.
About cross distribution&32/64bit ? I think it depends on the 32bit Libraries you have installed.
I haven't noticed limitations beside the 62/32bit limitation. I tried Debian64 , Debian32, Arch64, gentoo32, gentoo64- I can't remember an additional installed packaged to get it working.
Copy the imagebuilder file to a different place and extract it.
You can copy your own files into the image and/or install additional packages from the stock repository (and additional repositories you configure).
You have to be aware of the point, that with imagebuilder only a "bare-bone" image of the Yun-image is shipped. There is no web-interface and all the custom Yun packages are not included into that image, only the needed drivers to get the yun working. (That is the reason for asking in #21 what the original Yun packages are).
Hope that helps
And the specific profile (additional to packages above):
(Between all the other listed possible profiles).
At least the minimum Profile is there (OK).
You maybe can exclude the other profiles from your build-chain, because - as far as I recognized it - do changes in the "filesystem" without a target-profile dependency, right?
That leads me directly to my question in: #21
Thanks for you support, I really appreciate it!
@MaStr I now fully understand your need for a meta package. I'm not expert with the ImageBuilder, so I'm sorry but I won't be able to help much.
You can get the complete list of built-in packages with
Can you help us here?
@ffissore It is not a need , it is more like it is good to have, it would be better to have a description of the components you use on your image for specific things.
I just tested you config file. I would start from the end of the file and figure out the flagged packages, for this I just figured that command out
Then you get a long list with enabled packages:
The problem is, that you only see the flagged packages, but not why they are flagged. i.e. python depends on python-mini (I think). So you select in menuconfig "python" and python-mini is flagged too.
Now, you have to remember, why you activate a package like python-mini .
Do you have any self made packages in your repository?
Based upon those questions, I would try to create a dependency-list with additional meta-package like:
Sounds complicated in the first place compared to easily selecting it, but my idea behind is:
Let my know what you think
That information is lost once you select a package from the text UI
Yes, they are in https://github.com/arduino/openwrt-packages-yun,
It's a selected package
Those marked with "y" from this list
That's super good: can't wait to see it. Thank you!