1 Aug
2014
1 Aug
'14
11:45 a.m.
Hi.
Yesterday I set up a server with generic pre-compiled images for
LibreMesh. Find it here: http://downloads.libre-mesh.org/
ToDo: Set up the nightly compile, so we will have fresh compiled images
every night if there is some change in the code
--
./p4u
1 Aug
1 Aug
3:39 p.m.
----- Mensaje original -----
De: "Pau" <pau(a)dabax.net>
Para: "libre-mesh" <dev(a)lists.libre-mesh.org>
Enviados: Viernes, 1 de Agosto 2014 6:45:00
Asunto: [lime-dev] downloads.libre-mesh.org
Hi.
Yesterday I set up a server with generic pre-compiled images for
LibreMesh. Find it here: http://downloads.libre-mesh.org/
ToDo: Set up the nightly compile, so we will have fresh compiled
images
every night if there is some change in the code
--
./p4u
Good, but some issues:
* There's no "libre-mesh" on the name
* I think will be good to have openwrt revision number and libre-mesh revision number on
the name to know what are you using when you change it
* Remove uboot-ar71xx-nbg460n_550n_550nh/ directory (it's empty anyway)
2 Aug
2 Aug
12:51 p.m.
Thank you for the suggestions.
What you saw was actually the "raw" openwrt output directory, it can
also be used as repository for opkg (so you can install LiMe from raw
OpenWRT using opkg).
We should distinguish between two kind of binaries:
1) Official supported ones (those hardware which has been tested)
2) Unofficial generic ones (all OpenWRT supports but it has not been
tested)
If you go now to the downloads repository you will see there are new
images, these are the ones "officially supported", the generic are
inside the ar71xx directory.
El vie 01 ago 2014 17:39:04 CEST, al escribió:
----- Mensaje original -----
--
./p4u
De: "Pau" <pau(a)dabax.net>
Para: "libre-mesh" <dev(a)lists.libre-mesh.org>
Enviados: Viernes, 1 de Agosto 2014 6:45:00
Asunto: [lime-dev] downloads.libre-mesh.org
Hi.
Yesterday I set up a server with generic pre-compiled images for
LibreMesh. Find it here: http://downloads.libre-mesh.org/
ToDo: Set up the nightly compile, so we will have fresh compiled
images
every night if there is some change in the code
--
./p4u
Good, but some issues:
* There's no "libre-mesh" on the name
* I think will be good to have openwrt revision number and libre-mesh revision number on
the name to know what are you using when you change it
* Remove uboot-ar71xx-nbg460n_550n_550nh/ directory (it's empty anyway)
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
6:19 p.m.
On 02/08/14 07:51, Pau wrote:
Thank you for the suggestions.
What you saw was actually the "raw" openwrt output directory, it can
also be used as repository for opkg (so you can install LiMe from raw
OpenWRT using opkg).
We should distinguish between two kind of binaries:
1) Official supported ones (those hardware which has been tested)
2) Unofficial generic ones (all OpenWRT supports but it has not been
tested)
If you go now to the downloads repository you will see there are new
images, these are the ones "officially supported", the generic are
inside the ar71xx directory.
Great, but maybe OpenWrt people don't like that we offer OpenWrt as
"generic" when that "generic" have some of our modifications, I think
is
better to say that in that files.
> * There's no "libre-mesh" on the
name
Ok, now it's fixed.
> * I think will be good to have openwrt revision
number and libre-mesh revision number on the name to know what are you using when you
change it
Pending. Now they have data and time, I think it's not necessary
(because it's in metadata), but openwrt revision number and libre-mesh
revision number I think is so useful if we want to compare binary made
in that server with other ones that we made in our machines.
> * Remove uboot-ar71xx-nbg460n_550n_550nh/
directory (it's empty anyway)
Pending.
http://downloads.libre-mesh.org/develop/ar71xx/uboot-ar71xx-nbg460n_550n_55…
If you want I can help with this script generator of binaries.
7:23 p.m.
El sáb 02 ago 2014 20:19:42 CEST, al escribió:
I don't agree. For developers it would be interesting, but the users
only want to know which is the last version available in the
repository. Unfortunately the git revisions do not indicate which one
is newer and which is older, it is just a random hash. IMO having
revisions as reference for binaries is not a good idea.
What we can include is a text file in the repository with the relation
Date -> Revision, so in case of need anyone can go there and see which
is the revision number for such binary name.
On 02/08/14 07:51, Pau wrote:
I don't think they care, and the name "generic" is anywhere in the
repository. The directory is just named "ar71xx" and it is under the
"libre-mesh.org" domain, so I don't think it is gonna cause any
confusion.
Thank you for the suggestions.
What you saw was actually the "raw" openwrt output directory, it can
also be used as repository for opkg (so you can install LiMe from raw
OpenWRT using opkg).
We should distinguish between two kind of binaries:
1) Official supported ones (those hardware which has been tested)
2) Unofficial generic ones (all OpenWRT supports but it has not been
tested)
If you go now to the downloads repository you will see there are new
images, these are the ones "officially supported", the generic are
inside the ar71xx directory.
Great, but maybe OpenWrt people don't like that we offer OpenWrt as
"generic" when that "generic" have some of our modifications, I think
is
better to say that in that files. > *
There's no "libre-mesh" on the name
Ok, now it's fixed.
> * I think will be good to have openwrt
revision number and libre-mesh revision number on the name to know what are you using when
you change it
Pending. Now they have data and time, I think it's not necessary
(because it's in metadata), but openwrt revision number and libre-mesh
revision number I think is so useful if we want to compare binary made
in that server with other ones that we made in our machines. >> * Remove uboot-ar71xx-nbg460n_550n_550nh/
directory (it's empty anyway)
Came on, it is not so annoying :( It is created by OpenWRT buildroot,
and the ar71xx directory is the raw output directory of OpenWRT, so why
shall we remove it? For other architectures there will be probably more
empty directories, making a list of all of them may be annoying and IMO
a waste of time.
Pending.
http://downloads.libre-mesh.org/develop/ar71xx/uboot-ar71xx-nbg460n_550n_55…
If you want I can help with this script generator of binaries.
Sure, I'll push it to the lime-build repository.
--
./p4u
7:32 p.m.
Here you go:
https://github.com/libre-mesh/lime-build/blob/master/nightlycompile.sh
El s�b 02 ago 2014 21:23:51 CEST, Pau escribió:
El sáb 02 ago 2014 20:19:42 CEST, al escribió:
I don't agree. For developers it would be interesting, but the users
only want to know which is the last version available in the
repository. Unfortunately the git revisions do not indicate which one
is newer and which is older, it is just a random hash. IMO having
revisions as reference for binaries is not a good idea.
What we can include is a text file in the repository with the relation
Date -> Revision, so in case of need anyone can go there and see which
is the revision number for such binary name.
--
./p4u
On 02/08/14 07:51, Pau wrote:
I don't think they care, and the name "generic" is anywhere in the
repository. The directory is just named "ar71xx" and it is under the
"libre-mesh.org" domain, so I don't think it is gonna cause any
confusion.
Thank you for the suggestions.
What you saw was actually the "raw" openwrt output directory, it can
also be used as repository for opkg (so you can install LiMe from raw
OpenWRT using opkg).
We should distinguish between two kind of binaries:
1) Official supported ones (those hardware which has been tested)
2) Unofficial generic ones (all OpenWRT supports but it has not been
tested)
If you go now to the downloads repository you will see there are new
images, these are the ones "officially supported", the generic are
inside the ar71xx directory.
Great, but maybe OpenWrt people don't like that we offer OpenWrt as
"generic" when that "generic" have some of our modifications, I think
is
better to say that in that files. > *
There's no "libre-mesh" on the name
Ok, now it's fixed.
> * I think will be good to have openwrt
revision number and libre-mesh revision number on the name to know what are you using when
you change it
Pending. Now they have data and time, I think it's not necessary
(because it's in metadata), but openwrt revision number and libre-mesh
revision number I think is so useful if we want to compare binary made
in that server with other ones that we made in our machines. >> * Remove uboot-ar71xx-nbg460n_550n_550nh/
directory (it's empty anyway)
Came on, it is not so annoying :( It is created by OpenWRT buildroot,
and the ar71xx directory is the raw output directory of OpenWRT, so why
shall we remove it? For other architectures there will be probably more
empty directories, making a list of all of them may be annoying and IMO
a waste of time.
Pending.
http://downloads.libre-mesh.org/develop/ar71xx/uboot-ar71xx-nbg460n_550n_55…
If you want I can help with this script generator of binaries.
Sure, I'll push it to the lime-build repository.
--
./p4u
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
3794
days inactive
3795
days old
5 comments
2 participants
participants (2)
-
al -
Pau