Binary Packages » History » Version 4
neels, 10/30/2017 05:35 PM
| 1 | 1 | laforge | h1. Binary Packages |
|---|---|---|---|
| 2 | |||
| 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 | h2. Latest Versions |
||
| 6 | |||
| 7 | 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 | |||
| 9 | We recommend users to use the _latest_ package feeds for most normal use cases. |
||
| 10 | |||
| 11 | See [[Latest_Builds]] for more information on how to use those builds. |
||
| 12 | |||
| 13 | h2. Nightly Builds |
||
| 14 | |||
| 15 | 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 | |||
| 17 | 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 | |||
| 19 | See [[Nightly_Builds]] for more information on how to use those builds. |
||
| 20 | 3 | laforge | |
| 21 | h2. Stable Releases |
||
| 22 | |||
| 23 | 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 | |||
| 25 | 4 | neels | At this point, we don't yet have the resources to maintain stable releases. If you require stable releases and would like to contribute with manpower or financially, please do let us know. |
