Project

General

Profile

Binary Packages » History » Version 3

laforge, 10/28/2017 08:58 PM
stable releases

1 1 laforge
h1. Binary Packages
2 1 laforge
3 2 laforge
Unless you're a developer and understand how to build a set of programs and libraries from source code using GNU autotools, we strongly suggest you use the binary packages provided by Osmocom.
4 1 laforge
5 1 laforge
h2. Latest Versions
6 1 laforge
7 1 laforge
Osmocom maintains a set of binary packages that reflect the _latest tagged versions as per the version tags in the source git repository_.  They are called *network:osmocom:latest*.
8 1 laforge
9 1 laforge
We recommend users to use the _latest_ package feeds for most normal use cases.
10 1 laforge
11 1 laforge
See [[Latest_Builds]] for more information on how to use those builds.
12 1 laforge
13 1 laforge
h2. Nightly Builds
14 1 laforge
15 1 laforge
Osmocom maintains another set of binary packages that are automatically built once every 24 hours from the _master of the source git repository_.  They are called *network:osmocom:nightly*.
16 1 laforge
17 1 laforge
We recommend users to use nightly builds only if they want to stay with the bleeding edge, e.g. to test some bug fixes or new features that just were merged into master.
18 1 laforge
19 1 laforge
See [[Nightly_Builds]] for more information on how to use those builds.
20 3 laforge
21 3 laforge
h2. Stable Releases
22 3 laforge
23 3 laforge
The Osmocom project is planning to offer *stable releases* at some point in the future.  A *stable release* would be one specific set of packages across all repositories.  Releases would get maintenance and bug fixes for some time.
24 3 laforge
 
25 3 laforge
At this point, we don't yet have the resources to maintain stable releases.  If you requires stable releases and would like to contribute with manpower or financially, please do let us know.
Add picture from clipboard (Maximum size: 48.8 MB)