in various parts of lime-packages I found the following code snipped:
@rm -rf ./build || true
@cp -r ./src ./build
@sed -i '/^--!.*/d' build/*.lua
It removes all comments from the source code before applying it to the
Is the size impact worth the fact that
a) people locally developing may accidentally change files in ./build
rather then ./src and by running make overwriting all their changes
b) Make on device developing harder due to missing comments?
I'm guessing there are other parts of LibreMesh bloated which could
improve storage footprint more than this little hack, what do you think?
I pushed a new branch to libremesh/lime-packages called master.
We should from now on use this one instead of develop. I'd the scripts
of lime-sdk to use this branch in develop mode.
To clean up the outdated branches and repositories of /libremesh please
grant me the required GitHub permissions.
we got a new snapshots server which can host (and build) CI stuff.
I created a travis CI script so on each push it's building all LiMe
packages and uploads them to the server.
The LibreRouter specific stuff is also mirrored there. Whoever needs
access to update these files please ping me.
Who is in charge of the libremesh.org domain? Please forward
dealing lately a bit with CI and build packages for all popular targets
I found that most LiMe packages only use scripts like Lua and Bash and
therefore don't really need to be compiled target specific.
Idea is to add the PKGARCH:=all parameter which allows to install
resulting packages on all targets without opkg protesting.
I created an Pull request for that, please try! You can simply add
`.diff` to the url and receive a diff which is usable with `git apply
Eventually we could offer generic feeds in the
`/etc/opkg/limefeeds.conf` file and save a lot of build time.
A few packages actually require compiling and are thereby not arch
Are the first two packages actively used? I've never stumbled across them.