I haven't been able to build successfully yet using lime-build, I'm guessing because of this. Also agree that it is an important thing to address.

I took the liberty of creating an issue on Github, <https://github.com/libre-mesh/lime-packages/issues/50>. I'm sure someone else can resolve it faster, but I'll try to look into this later this week if nobody else has. Sorry, if posting to Github isn't proper protocol.

marvin

On 07/10/2016 12:48 PM, Ilario Gelmetti wrote:
On 05/05/2016 03:19 PM, Ilario wrote:

As pointed out in the LiMeCat notes, Chef adds to Libre-Mesh a few scripts.
Some of these are needed for Chef to customize the build, some others
should be included in lime-packages if we want lime-build to produce
images as good as the ones from chef.

For example
    /etc/uci-defaults/95_add-sshkeys
    /etc/config/lime-defaults
    /etc/chef_version
are needed for some of the customization features of chef (but the
lime-defaults file should be up to date with the one in
lime-packages).I

While *in my opinion* these files should be moved from chef to
somewhere in lime-packages:
    /usr/sbin/reset_deaf_phys.sh
    /etc/uci-defaults/93_enable-reset-deaf-phys
    /etc/config/libremap
    /etc/uci-defaults/93_ugly-fixes
    /etc/uci-defaults/95_reboot-daily
    /etc/uci-defaults/95_snmpd
    /etc/uci-defaults/95_set-timezone
    /etc/uci-defaults/95_set-remote-syslog

Gui, is there some of these files we can skip as won't be useful in
the next stable release?

Hey...
I resurrect this issue I consider very important to address before the
next stable release.
You can find attached the files included by chef in the Libre-Mesh
images (neither present in lime-build nor in lime-packages).
Bye!
Ilario








_______________________________________________
Dev mailing list
Dev@lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev