[RECEIVED FROM EXTERNAL SENDER]
On 3/3/20 12:25 PM, amuza wrote:
> I have been out for a long while, and now I would like to resume my
> libremeshing. I don't remember many things, and I see the website did
> not change much.
>
> Is 17.06 still the recommended version?
>
> I remember when you wanted to precook binaries for your own network
> there was this chef thing you could use. Is that thing still available?
> I don't remember where it was.
>
> I'd be happy if you could give me some updates on versions,
> methodologies and URLs.
Hi!
As there was no answer on this topic in 20 days, I'll copy and paste
here spiccinini's answer that was posted on the Riot/Matrix chat [1] and
I'll add some more observations:
spiccinini wrote:
> some of us are mainly working in master, trying to maintain it as stable as possible. Many communities in south america have been using this "rolling un-release" libremesh firmwares.
>
> In my opinion we should performa a release based on 18.06 with what we have now, stating the current issues. But I know that not everyone has the same opinion (at least ilario and daniel).
>
> We currently don't have a way to colectively take decisions (for example to release or not, etc) other than the github pull requests. I would be very happy (and I beleave it will impact positively in the project) if we find a way to build a decision mechanism.
In my opinion it would be better to have an OpenWrt19.07-based release
but to have a OpenWrt18.06-based release is much much better than no
release at all (which is the current situation: LibreMesh17.06 is 3
years old now).
Chef backend and frontend is currently being rewritten by aparcar and
coworkers in a completely different shape [2,3] and anyway does not make
sense to have a Chef for something that is not a release.
So, currently the suggested compilation method is the one described on
the website on "Compiling LibreMesh from source code" [4].
The pending issues for making a release based on OpenWrt18.06 or on
OpenWrt19.07 does not differ much [5] but there is at least a
significant one regarding Batman-adv configuration.
I started selecting some high-priority issues which in my opinion would
be good to fix/implement before releasing [6]. Any contribution and
comment is welcome!
Hugs,
Ilario
[1]
https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flibremesh.org%2Fcommunication.html&data=01%7C01%7Cnickdark%40rowdentech.com%7Ce7a4740069c342e01b7e08d7cf41ef88%7C60ea4930b27d4dceac7e226adad375fd%7C0&sdata=%2FUWsI0psA41VFoh%2FCUXNGcJ1NnMDUUNZUr%2B0MJX2xhc%3D&reserved=0
[2]
https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Faparcar%2Fasu%2Fissues%2F211&data=01%7C01%7Cnickdark%40rowdentech.com%7Ce7a4740069c342e01b7e08d7cf41ef88%7C60ea4930b27d4dceac7e226adad375fd%7C0&sdata=X9ziYiXgCu8GpI0yK%2BUKtwtPWO1fREyHjh5gVQnwf7A%3D&reserved=0
[3]
https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Faparcar%2Fasu&data=01%7C01%7Cnickdark%40rowdentech.com%7Ce7a4740069c342e01b7e08d7cf41ef88%7C60ea4930b27d4dceac7e226adad375fd%7C0&sdata=PjUiVJocQzIoeADJAXbXADl3mco9sc05SCeiLV33sh0%3D&reserved=0
[4]
https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flibremesh.org%2Fdevelopment.html&data=01%7C01%7Cnickdark%40rowdentech.com%7Ce7a4740069c342e01b7e08d7cf41ef88%7C60ea4930b27d4dceac7e226adad375fd%7C0&sdata=vMYr6wi3W6h6n3PeYEZFBbbAS8Uwi2XrjbXp%2F1olerU%3D&reserved=0
[5]
https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flibremesh%2Flime-packages%2Flabels%2FOpenWrt%252019.07&data=01%7C01%7Cnickdark%40rowdentech.com%7Ce7a4740069c342e01b7e08d7cf41ef88%7C60ea4930b27d4dceac7e226adad375fd%7C0&sdata=JtEZwzSGEZfwgjvbEdinZ5FAZYa28QXzJV0tiZqQBmg%3D&reserved=0
[6]
https://gbr01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Forgs%2Flibremesh%2Fprojects%2F2&data=01%7C01%7Cnickdark%40rowdentech.com%7Ce7a4740069c342e01b7e08d7cf41ef88%7C60ea4930b27d4dceac7e226adad375fd%7C0&sdata=7RcIvygqYZwlIJi1EpdgFMlCatZtIRIsYg0OQPKwztE%3D&reserved=0
--
Ilario
iochesonome@gmail.com
ilario@sindominio.net