Repository: incubator-mynewt-site Updated Branches: refs/heads/asf-site 90d67204d -> bb4af1c86
Merge branch 'MYNEWT-260' of https://github.com/paulfdietrich/incubator-mynewt-site plus minor edits Project: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/commit/bb4af1c8 Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/bb4af1c8 Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/bb4af1c8 Branch: refs/heads/asf-site Commit: bb4af1c86356142cfdd394101e9d523bd9fbcc1b Parents: 90d6720 Author: aditihilbert <[email protected]> Authored: Fri Mar 18 10:07:06 2016 -0700 Committer: aditihilbert <[email protected]> Committed: Fri Mar 18 10:07:06 2016 -0700 ---------------------------------------------------------------------- mkdocs/search_index.json | 55 ++ os/tutorials/STM32F303/index.html | 10 + os/tutorials/add_repos/index.html | 758 ++++++++++++++++++++++++ os/tutorials/air_quality_sensor/index.html | 10 + os/tutorials/arduino_zero/index.html | 10 + os/tutorials/how_to_edit_docs/index.html | 10 + os/tutorials/nRF52/index.html | 10 + os/tutorials/olimex/index.html | 10 + os/tutorials/tutorials/index.html | 10 + os/tutorials/unit_test/index.html | 10 + sitemap.xml | 22 +- 11 files changed, 904 insertions(+), 11 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bb4af1c8/mkdocs/search_index.json ---------------------------------------------------------------------- diff --git a/mkdocs/search_index.json b/mkdocs/search_index.json index 79a209d..a4eafd7 100644 --- a/mkdocs/search_index.json +++ b/mkdocs/search_index.json @@ -651,6 +651,61 @@ "title": "Local preview of HTML files" }, { + "location": "/os/tutorials/add_repos/", + "text": "Additional Repositories\n\n\nWhat is a Repository\n\n\nA repository is a version-ed Mynewt project, which is a \ncollection of Mynewt packages organized in a specific\nway. \n\n\nWhat differentiates a repository from a Mynewt project is the presence of a\n\nrepository.yml\n file describing the repository. This will be described \nbelow. \nNote:\n For the remainder of this document we'll use the term repo as shorthand for a \nMynewt repository.\n\n\nRepos are useful because they are an organized way for the community\nto share Mynewt packages and projects. In fact, the Mynewt-core is \ndistributed as a repo.\n\n\n\n\nWhy does Mynewt need additional repos?\n\n\nRepos add functionality not included in the Mynewt core. New repos might be created for \nseveral reasons.\n\n\n\n\nExpertise\n. Individuals or organizations may have expertise that they want\nto share in the form of repos. For example a chip vendor may\ncreate a repo to hold the Mynewt support for thei r chips.\n\n\nNon-Core component\n. Some components, although very useful to Mynewt users\nare not core to all Mynewt users. These are likely candidates to be held in \ndifferent repos.\n\n\nSoftware licensing\n. Some software have licenses that make them incompatible\nwith the ASF (Apache Software Foundation) license policies. These may be \nvaluable components to some Mynewt users, but cannot be contained in the \napache-Mynewt-core\n.\n\n\n\n\n\n\nWhat Repos are in my Project\n\n\nThe list of repos used by your project are contained within the \n\nproject.yml\n file. An example can be seen by creating a new project:\n\n\n$ mkdir ~/dev\n$ cd ~/dev\n$ newt new myproj\n$ cd myproj\n\n\n\n\n\n\n\nView the \nproject.yml\n section and you will see a line describing the repos:\n\n\nproject.repositories:\n - apache-Mynewt-core\n\n\n\n\n\n \n\n\nBy default, this newly created project uses a single repo called \n\napache-Mynewt-core\n. \n\n\nIf you wish to add additional repos, yo u would add \nadditional lines to the \nproject.repositories\n variable like this.\n\n\nproject.repositories:\n - apache-Mynewt-core\n - another_repo_named_x\n\n\n\n\n\n\n\nRepo Descriptors\n\n\nIn addition to the repo name, the \nproject.yml\n file must also contain\na repo descriptor for each repository you include that gives \nnewt\n \ninformation on obtaining the repo.\n\n\nIn the same \nmyproj\n above you will see the following repo descriptor.\n\n\nrepository.apache-Mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\nA repo descriptor starts with \nrepository.\nname\n.\n. In this example, the \ndescriptor specifies the information for the \napache-Mynewt-core\n.\n\n\n\n\nThe fields within the descriptor have the following definitions:\n\n\n\n\n\n\ntype\n -- The type of code storage the repo uses. The current version\nof \nnewt\n only supports github. Future versions may support generic git or other\ncode sto rage mechanisms.\n\n\n\n\n\n\nvers\n -- The version of the repo to use for your project. A source\ncode repository contains many versions of the source. This field is used to \nspecify the one to use for this project. See the section on versions below \nfor a detailed description of the format of this field.\n\n\n\n\n\n\nuser\n -- The username for the repo. On github, this is the name\nafter \ngithub.com\n in the repo path. Consider the repository \n\nhttps://github.com/apache/incubator-mynewt-core\n. It has username \napache\n. \n\n\n\n\n\n\nrepo\n -- The name of the repo. On github, this is the name after\nthe username described above. Consider the repository \n\nhttps://github.com/apache/incubator-mynewt-core\n. It has username \n\nincubator-mynewt-core\n. This is a path to the source control\nand should not be confused with the name of the repo that you used in the \n\nrepository.\nname\n declaration above. That name is contained elsewhere\nwithin the repo. See Below.\ n\n\n\n\n\n\n\n\nAdding Existing Repos to my Project\n\n\nTo add a new repo to your project, you have to complete two steps.\n\n\n\n\n\n\nEdit the \nproject.yml\n file and add a new repo descriptor. The previous\nsection includes information on the field required in your repo descriptor.\n\n\n\n\n\n\nEdit the \nproject/yml\n file and add a new line to the \nproject.repositories\n\nvariable with the name of the repo you are adding. \n\n\n\n\n\n\nAn example if a \nproject.yml\n file with two repositories is shown below:\n\n\nproject.name: \nmy_project\n\n\nproject.repositories:\n - apache-Mynewt-core\n - Mynewt_arduino_zero\n\n# Use github\ns distribution mechanism for core ASF libraries.\n# This provides mirroring automatically for us.\n#\nrepository.apache-Mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core\n\n# a special repo to hold hardware specific stuff for arduino zero\nrepository.Mynewt_arduino_zero:\n type: github\ n vers: 0-latest\n user: runtimeinc\n repo: Mynewt_arduino_zero\n\n\n\n\n\n\n\nWhat Version of the Repo to use\n\n\nMynewt repos are version-ed artifacts. They are stored in source control \nsystems like github. The repo descriptor in your \nproject.yml\n file must\nspecify the version of the repo you will accept into your project.\n\n\nFor now, we are at the beginnings of Mynewt. For testing and evaluation\nplease use \n0-latest\n in the \nvers\n field in your repo descriptor.\n\n\n vers:0-latest\n\n\n\n\n\nSee below for a description of the version system.\n\n\n\n\nWhat is in a Repo\n\n\nA repo is a collection of Mynewt packages organized in a specific\nway and stored in one of the supported code storage methods described above. \n\n\nA repo is a Mynewt project with an additional file \nrepository.yml\n\nwhich describes the repo for use by \nnewt\n (and humans browsing them).\n\n\nThere is one key consideration for this \nrepository.yml\n file. The \n\nrepository.ym l\n file only lives in the master branch of the git\nrepository. \nNewt\n will always fetch this file from the master branch and then\nuse that to resolve the actual branch required depending on the version\nspecified in the project. Special care should be taken to ensure that this\nfile exists only in the master branch.\n\n\nHere is the \nrepository.yml\n file from the apache-Mynewt-core:\n\n\nrepo.name: apache-mynewt-core\nrepo.versions:\n \n0.7.9\n: \nMynewt_0_8_0_b2_tag\n\n \n0-latest\n: \n0.7.9\n\n \n0.8-latest\n: \n0.7.9\n\n\n\n\n\n\n\n\nIt contains the following:\n\n\n\n\nrepo.name\n The external name that is used to include the library in \nyour \nproject.yml\n file. This is the name you in include in the \nproject.repositories\n variable when adding this repository to your project.\n\n\nrepo.versions\n A description of what versions to give the user depending \non the settings in their \nproject.yml\n file. See below for a thorough description\non versioning. Its a flexible mapping between version numbers and git branches.\n\n\n\n\n\n\nRepo Version\n\n\nThe version field argument in your \nproject.yml\n file has the following format:\n\n\nmajor_num\n.\nminor_num\n.\nrevision_num\n\n\n\n\n\n\nor\n\n\nmajor_num\n.\nminor_num\n-\nstability string\n\n\n\n\n\n\nor \n\n\nmajor_num\n-\nstability string\n\n\n\n\n\n\n\n\nThe stability string can be one of 3 pre-defined stability values.\n\n\n\n\nstable -- A stable release version of the repository\n\n\ndev -- A development version from the repository\n\n\nlatest -- The latest from the repository\n\n\n\n\nIn your \nproject.yml\n file you can specify different combinations of \nthe version number and stability value. For example:\n\n\n\n\n0-latest\n -- The latest version with major number 0\n\n\n1.2-stable\n -- The latest stable version with major and minor number 1.2\n\n\n1.2-dev\n -- The development version from 1.2\n\n\n1.1.1\n -- a specific version 1.1.1\n\n\n\n\nYou c annot specify a stability string with a fully numbered version, e.g.\n\n\n1.2.8-stable\n\n\n\n\n\n\n\nA \nrepository.yml\n file contains information to match this version request\ninto a git branch to fetch for your project.\n\n\nIts up to the repository maintainer to map these to branches of the \nrepository. For example, let's say in a fictitious repository the following are \ndefined.\n\n\nrepo.versions:\n \n0.8.0\n: \nxxx_branch_0_8_0\n\n \n1.0.0\n: \nxxx_branch_1_0_0\n\n \n1.0.2\n: \nxxx_branch_1_0_2\n\n \n1.1.1\n: \nxxx_branch_1_1_0\n\n \n1.1.2\n: \nxxx_branch_1_1_2\n\n \n1.2.0\n: \nxxx_branch_1_2_0\n\n \n1.2.1\n: \nxxx_branch_1_2_1\n\n \n1.2-dev\n: \n1.2.1\n\n \n1-dev\n: \n1.2-dev\n\n \n1.2-stable\n: \n1.2.0\n\n \n0-latest\n: \n0.8.0\n\n \n1-latest\n: \n1-dev\n\n ....\n\n\n\n\n\nWhen the \nproject.yml\n file asks for \n1.2-stable\n its resolved to version\n\n1.2.0\n (perhaps \n1.2.1\n is not stable yet), which resolves to a specific\nbr anch \nxxx_branch_1_2_0\n. This is the branch that \nnewt\n fetches into \nyour project.\n\n\n\n\nHow to find out what Repos are available for Mynewt components\n\n\nCurrently, there is no \nnewt\n command to locate/search Mynewt package \nrepositories. However, since the \nnewt\n tool supports only github, \nsearching github by keyword is a satisfactory option until a search \ntool is created.\n\n\nWhen searching github, recall that a Mynewt repository must \nhave a \nrepository.yml\n file in its root directory. If you don't see \nthat file, it's not a Mynewt repository and can't be included in your \nproject via the newt tool. \n\n\nOnce you find a repository, the github URL and \nrepository.yml\n file\nshould give you all the information to add it to your \nproject.yml\n file.", + "title": "Additional Repositories" + }, + { + "location": "/os/tutorials/add_repos/#additional-repositories", + "text": "", + "title": "Additional Repositories" + }, + { + "location": "/os/tutorials/add_repos/#what-is-a-repository", + "text": "A repository is a version-ed Mynewt project, which is a \ncollection of Mynewt packages organized in a specific\nway. What differentiates a repository from a Mynewt project is the presence of a repository.yml file describing the repository. This will be described \nbelow. Note: For the remainder of this document we'll use the term repo as shorthand for a \nMynewt repository. Repos are useful because they are an organized way for the community\nto share Mynewt packages and projects. In fact, the Mynewt-core is \ndistributed as a repo.", + "title": "What is a Repository" + }, + { + "location": "/os/tutorials/add_repos/#why-does-mynewt-need-additional-repos", + "text": "Repos add functionality not included in the Mynewt core. New repos might be created for \nseveral reasons. Expertise . Individuals or organizations may have expertise that they want\nto share in the form of repos. For example a chip vendor may\ncreate a repo to hold the Mynewt support for their chips. Non-Core component . Some components, although very useful to Mynewt users\nare not core to all Mynewt users. These are likely candidates to be held in \ndifferent repos. Software licensing . Some software have licenses that make them incompatible\nwith the ASF (Apache Software Foundation) license policies. These may be \nvaluable components to some Mynewt users, but cannot be contained in the apache-Mynewt-core .", + "title": "Why does Mynewt need additional repos?" + }, + { + "location": "/os/tutorials/add_repos/#what-repos-are-in-my-project", + "text": "The list of repos used by your project are contained within the project.yml file. An example can be seen by creating a new project: $ mkdir ~/dev\n$ cd ~/dev\n$ newt new myproj\n$ cd myproj View the project.yml section and you will see a line describing the repos: project.repositories:\n - apache-Mynewt-core By default, this newly created project uses a single repo called apache-Mynewt-core . If you wish to add additional repos, you would add \nadditional lines to the project.repositories variable like this. project.repositories:\n - apache-Mynewt-core\n - another_repo_named_x", + "title": "What Repos are in my Project" + }, + { + "location": "/os/tutorials/add_repos/#repo-descriptors", + "text": "In addition to the repo name, the project.yml file must also contain\na repo descriptor for each repository you include that gives newt \ninformation on obtaining the repo. In the same myproj above you will see the following repo descriptor. repository.apache-Mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core A repo descriptor starts with repository. name . . In this example, the \ndescriptor specifies the information for the apache-Mynewt-core . The fields within the descriptor have the following definitions: type -- The type of code storage the repo uses. The current version\nof newt only supports github. Future versions may support generic git or other\ncode storage mechanisms. vers -- The version of the repo to use for your project. A source\ncode repository contains many versions of the source. This field is used to \nspecify the one to use for this project. See the section on ve rsions below \nfor a detailed description of the format of this field. user -- The username for the repo. On github, this is the name\nafter github.com in the repo path. Consider the repository https://github.com/apache/incubator-mynewt-core . It has username apache . repo -- The name of the repo. On github, this is the name after\nthe username described above. Consider the repository https://github.com/apache/incubator-mynewt-core . It has username incubator-mynewt-core . This is a path to the source control\nand should not be confused with the name of the repo that you used in the repository. name declaration above. That name is contained elsewhere\nwithin the repo. See Below.", + "title": "Repo Descriptors" + }, + { + "location": "/os/tutorials/add_repos/#adding-existing-repos-to-my-project", + "text": "To add a new repo to your project, you have to complete two steps. Edit the project.yml file and add a new repo descriptor. The previous\nsection includes information on the field required in your repo descriptor. Edit the project/yml file and add a new line to the project.repositories \nvariable with the name of the repo you are adding. An example if a project.yml file with two repositories is shown below: project.name: my_project \n\nproject.repositories:\n - apache-Mynewt-core\n - Mynewt_arduino_zero\n\n# Use github s distribution mechanism for core ASF libraries.\n# This provides mirroring automatically for us.\n#\nrepository.apache-Mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core\n\n# a special repo to hold hardware specific stuff for arduino zero\nrepository.Mynewt_arduino_zero:\n type: github\n vers: 0-latest\n user: runtimeinc\n repo: Mynewt_arduino_zero", + "title": "Adding Existing Repos to my Project" + }, + { + "location": "/os/tutorials/add_repos/#what-version-of-the-repo-to-use", + "text": "Mynewt repos are version-ed artifacts. They are stored in source control \nsystems like github. The repo descriptor in your project.yml file must\nspecify the version of the repo you will accept into your project. For now, we are at the beginnings of Mynewt. For testing and evaluation\nplease use 0-latest in the vers field in your repo descriptor. vers:0-latest See below for a description of the version system.", + "title": "What Version of the Repo to use" + }, + { + "location": "/os/tutorials/add_repos/#what-is-in-a-repo", + "text": "A repo is a collection of Mynewt packages organized in a specific\nway and stored in one of the supported code storage methods described above. A repo is a Mynewt project with an additional file repository.yml \nwhich describes the repo for use by newt (and humans browsing them). There is one key consideration for this repository.yml file. The repository.yml file only lives in the master branch of the git\nrepository. Newt will always fetch this file from the master branch and then\nuse that to resolve the actual branch required depending on the version\nspecified in the project. Special care should be taken to ensure that this\nfile exists only in the master branch. Here is the repository.yml file from the apache-Mynewt-core: repo.name: apache-mynewt-core\nrepo.versions:\n 0.7.9 : Mynewt_0_8_0_b2_tag \n 0-latest : 0.7.9 \n 0.8-latest : 0.7.9 It contains the following: repo.name The external name that is used to include th e library in \nyour project.yml file. This is the name you in include in the project.repositories variable when adding this repository to your project. repo.versions A description of what versions to give the user depending \non the settings in their project.yml file. See below for a thorough description\non versioning. Its a flexible mapping between version numbers and git branches.", + "title": "What is in a Repo" + }, + { + "location": "/os/tutorials/add_repos/#repo-version", + "text": "The version field argument in your project.yml file has the following format: major_num . minor_num . revision_num or major_num . minor_num - stability string or major_num - stability string The stability string can be one of 3 pre-defined stability values. stable -- A stable release version of the repository dev -- A development version from the repository latest -- The latest from the repository In your project.yml file you can specify different combinations of \nthe version number and stability value. For example: 0-latest -- The latest version with major number 0 1.2-stable -- The latest stable version with major and minor number 1.2 1.2-dev -- The development version from 1.2 1.1.1 -- a specific version 1.1.1 You cannot specify a stability string with a fully numbered version, e.g. 1.2.8-stable A repository.yml file contains information to match this version request\ninto a git branch to fetch f or your project. Its up to the repository maintainer to map these to branches of the \nrepository. For example, let's say in a fictitious repository the following are \ndefined. repo.versions:\n 0.8.0 : xxx_branch_0_8_0 \n 1.0.0 : xxx_branch_1_0_0 \n 1.0.2 : xxx_branch_1_0_2 \n 1.1.1 : xxx_branch_1_1_0 \n 1.1.2 : xxx_branch_1_1_2 \n 1.2.0 : xxx_branch_1_2_0 \n 1.2.1 : xxx_branch_1_2_1 \n 1.2-dev : 1.2.1 \n 1-dev : 1.2-dev \n 1.2-stable : 1.2.0 \n 0-latest : 0.8.0 \n 1-latest : 1-dev \n .... When the project.yml file asks for 1.2-stable its resolved to version 1.2.0 (perhaps 1.2.1 is not stable yet), which resolves to a specific\nbranch xxx_branch_1_2_0 . This is the branch that newt fetches into \nyour project.", + "title": "Repo Version" + }, + { + "location": "/os/tutorials/add_repos/#how-to-find-out-what-repos-are-available-for-mynewt-components", + "text": "Currently, there is no newt command to locate/search Mynewt package \nrepositories. However, since the newt tool supports only github, \nsearching github by keyword is a satisfactory option until a search \ntool is created. When searching github, recall that a Mynewt repository must \nhave a repository.yml file in its root directory. If you don't see \nthat file, it's not a Mynewt repository and can't be included in your \nproject via the newt tool. Once you find a repository, the github URL and repository.yml file\nshould give you all the information to add it to your project.yml file.", + "title": "How to find out what Repos are available for Mynewt components" + }, + { "location": "/os/os_user_guide/", "text": "OS User Guide\n\n\nThis guide provides comprehensive information about Mynewt OS, the real-time operating system for embedded systems.\n\n\nIt is intended both for an embedded real-time software developer as well as higher-level applications developer wanting to understand the features and benefits of the system. \n\n\nMynewt OS is highly composable and flexible. Only those features actually used by the application are compiled into the run-time image. Hence, the actual size of Mynewt is completely determined by the application. The guide covers all the features and services available in the OS and contains several examples showing how they can be used.\n\n\nSend us an email on the dev@ mailing list if you have comments or suggestions!\n If you haven't joined the mailing list, you will find the links \nhere\n.", "title": "toc" http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bb4af1c8/os/tutorials/STM32F303/index.html ---------------------------------------------------------------------- diff --git a/os/tutorials/STM32F303/index.html b/os/tutorials/STM32F303/index.html index 5622728..a0c93dc 100644 --- a/os/tutorials/STM32F303/index.html +++ b/os/tutorials/STM32F303/index.html @@ -300,6 +300,16 @@ + + + + <li> + <a href="../add_repos/">Additional Repositories</a> + </li> + + + + </ul> </li> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bb4af1c8/os/tutorials/add_repos/index.html ---------------------------------------------------------------------- diff --git a/os/tutorials/add_repos/index.html b/os/tutorials/add_repos/index.html new file mode 100644 index 0000000..9c61f81 --- /dev/null +++ b/os/tutorials/add_repos/index.html @@ -0,0 +1,758 @@ +<!DOCTYPE html> +<html lang="en"> + <head> + <meta charset="utf-8"> + <meta http-equiv="X-UA-Compatible" content="IE=edge"> + <meta name="viewport" content="width=device-width, initial-scale=1.0"> + + + <link rel="canonical" href="http://mynewt.apache.org/os/tutorials/add_repos/";> + <link rel="shortcut icon" href="../../../img/favicon.ico"> + + <title>Additional Repositories - Apache Mynewt</title> + + <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet"> + <link href="../../../css/font-awesome-4.0.3.css" rel="stylesheet"> + <link rel="stylesheet" href="../../../css/highlight.css"> + <link href="../../../css/base.css" rel="stylesheet"> + <link href="../../../css/custom.css" rel="stylesheet"> + <link href='https://fonts.googleapis.com/css?family=Roboto:400,500,700,900,300,100' rel='stylesheet' type='text/css'> + <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css";> + <link href="../../../extra.css" rel="stylesheet"> + + <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries --> + <!--[if lt IE 9]> + <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js";></script> + <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js";></script> + <![endif]--> + + + <script> + (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ + (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), + m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) + })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); + + ga('create', 'UA-72162311-1', 'mynewt.incubator.apache.org'); + ga('send', 'pageview'); + </script> + + </head> + + + <body class="Additional Repositories"> + + + <div id="navbar" class="navbar navbar-default navbar-fixed-top" role="navigation"> + <div class="logo-container"> + <img src="/img/logo.svg"> + </div> + <div class="container-fluid"> + <!-- Collapsed navigation --> + <div class="navbar-header"> + <!-- Expander button --> + <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse"> + <span class="sr-only">Toggle navigation</span> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + </button> + + </div> + + <!-- Expanded navigation --> + <div class="navbar-collapse collapse"> + <!-- Main navigation --> + <ul class="nav navbar-nav navbar-right"> + <li> + <a href="/">Home</a> + </li> + <li> + <a href="/about/">About</a> + </li> + <li class="dropdown"> + <a href="/documentation/" class="dropdown-toggle" data-toggle="dropdown">Docs <b class="caret"></b></a> + <ul class="dropdown-menu"> + + + + + + + <li > + <a href="../../../documentation/"> + Overview + </a> + </li> + + + + + + + + + + <li class="active"> + <a href="../../get_started/introduction/"> + Mynewt OS Manual + </a> + </li> + + + + <li > + <a href="../../../newt/newt_intro/"> + Newt Tool Manual + </a> + </li> + + + + <li > + <a href="../../../newtmgr/overview/"> + Newt Manager Manual + </a> + </li> + + + + <li > + <a href="../../../faq/answers/"> + Appendix + </a> + </li> + + + </ul> + </li> + <li> + <a href="/download/">Download</a> + </li> + <li> + <a href="/community/">Community</a> + </li> + <li> + <a href="/events/">Events</a> + </li> + </ul> + + <!-- Search, Navigation and Repo links --> + <ul class="nav navbar-nav navbar-right"> + + </ul> + </div> + </div> +</div> + + + + <div class="container-fluid"> + + <div class="row sm-extra-padding"> + <div id="docSidebar" class="col-md-3 bg-grey sidebar-container"><div class="bs-sidebar hidden-print" role="complementary"> + <div class="sidebar-top"> + <img class="hidden-xs hidden-sm logo-small" src="/img/logo.svg" alt="MyNewt" title="MyNewt"> + <div class="small" role="search"> + <form id ="rtd-search-form" class="wy-form" action="../../../search.html" method="get"> + <div class="form-group"> + <input type="text" name="q" placeholder="Search documentation" /> + <button class="search-button" type="submit"><i class="fa fa-search"></i></button> + </div> + </form> + </div> + </div> + <ul class="nav bs-sidenav"> + + + + + + + + + + + + + + + + + + <li><a href=" + ../../get_started/introduction/ +">Mynewt OS Manual</a> + + + <ul class="current-toc"> + + + + + <li> + <a href="../../get_started/introduction/">Introduction</a> + </li> + + + + + + + + + <li ><a href="../../get_started/get_started/">Quick Start</a></li> + + + </li> + + + + + + + + <li ><a href="../../get_started/vocabulary/">Concepts</a></li> + + + </li> + + + + + + + + <li ><a href="../tutorials/">Tutorials</a></li> + + + <ul class="current-toc"> + + + + + + + <li> + <a href="../arduino_zero/">Blinky on Arduino Zero</a> + </li> + + + + + + + + <li> + <a href="../olimex/">Blinky on Olimex</a> + </li> + + + + + + + + <li> + <a href="../STM32F303/">Blinky on STM32F303</a> + </li> + + + + + + + + <li> + <a href="../nRF52/">Blinky on nRF52</a> + </li> + + + + + + + + <li> + <a href="../unit_test/">Write a Test Suite for a Package</a> + </li> + + + + + + + + <li> + <a href="../air_quality_sensor/">Air-quality Sensor project</a> + </li> + + + + + + + + <li> + <a href="../how_to_edit_docs/">Edit Docs</a> + </li> + + + + + + + + <li class="active"> + Additional Repositories + </li> + + + + + </ul> + + </li> + + + + + + + + <li ><a href="../../os_user_guide/">OS User Guide</a></li> + + + </li> + + + + + + + + <li><a href=" + + + ../../../network/ble/ble_intro/ + +">Networking User Guide</a> + + + </li> + + + + </ul> + + </li> + + + + + + + + <li><a href=" + ../../../newt/newt_intro/ +">Newt Tool Manual</a> + + + </li> + + + + + + + + <li><a href=" + ../../../newtmgr/overview/ +">Newt Manager Manual</a> + + + </li> + + + + + + + + <li><a href=" + ../../../faq/answers/ +">Appendix</a> + + + </li> + + + + </ul> +</div></div> + + <div class="show-sidebar-container"> + <button class="show-sidebar">Docs Menu</button> + </div> + + <div class="col-md-offset-3 col-md-9 documentation-viewer" role="main"> + <div class="row doc-header"> + <div class="col-sm-6"> + +<ul class="nav nav-pills"> + + + + + + + + + + + + + + + + + <li class="active" role="presentation"><a href="../../get_started/introduction/">Mynewt OS</a></li> + + + + <li role="presentation"><a href="../../../newt/newt_intro/">Newt Tool</a></li> + + + + <li role="presentation"><a href="../../../newtmgr/overview/">Newt Mgr</a></li> + + + + +</ul> + </div> + <div class="col-sm-6"> + <div role="navigation" aria-label="breadcrumbs navigation"> + <ul class="wy-breadcrumbs"> + <li><a href="/documentation/">Docs</a></li> + + + + <li>» <a href="../../get_started/introduction/">Mynewt OS Manual</a></li> + + + + <li>» <a href="../tutorials/">Tutorials</a></li> + + + + <li>» Additional Repositories</li> + + + + </ul> +</div> + </div> + </div> + + <h2 id="additional-repositories">Additional Repositories<a class="headerlink" href="#additional-repositories" title="Permanent link">¶</a></h2> +<h3 id="what-is-a-repository">What is a Repository<a class="headerlink" href="#what-is-a-repository" title="Permanent link">¶</a></h3> +<p>A repository is a version-ed Mynewt project, which is a +collection of Mynewt packages organized in a specific +way. </p> +<p>What differentiates a repository from a Mynewt project is the presence of a +<code>repository.yml</code> file describing the repository. This will be described +below. <strong>Note:</strong> For the remainder of this document we'll use the term repo as shorthand for a +Mynewt repository.</p> +<p>Repos are useful because they are an organized way for the community +to share Mynewt packages and projects. In fact, the Mynewt-core is +distributed as a repo.</p> +<p><br></p> +<h3 id="why-does-mynewt-need-additional-repos">Why does Mynewt need additional repos?<a class="headerlink" href="#why-does-mynewt-need-additional-repos" title="Permanent link">¶</a></h3> +<p>Repos add functionality not included in the Mynewt core. New repos might be created for +several reasons.</p> +<ul> +<li><strong>Expertise</strong>. Individuals or organizations may have expertise that they want +to share in the form of repos. For example a chip vendor may +create a repo to hold the Mynewt support for their chips.</li> +<li><strong>Non-Core component</strong>. Some components, although very useful to Mynewt users +are not core to all Mynewt users. These are likely candidates to be held in +different repos.</li> +<li><strong>Software licensing</strong>. Some software have licenses that make them incompatible +with the ASF (Apache Software Foundation) license policies. These may be +valuable components to some Mynewt users, but cannot be contained in the <code>apache-Mynewt-core</code>.</li> +</ul> +<p><br></p> +<h3 id="what-repos-are-in-my-project">What Repos are in my Project<a class="headerlink" href="#what-repos-are-in-my-project" title="Permanent link">¶</a></h3> +<p>The list of repos used by your project are contained within the +<code>project.yml</code> file. An example can be seen by creating a new project:</p> +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ mkdir ~/dev +$ cd ~/dev +$ newt new myproj +$ cd myproj +</pre></div> + + +<p><br></p> +<p>View the <code>project.yml</code> section and you will see a line describing the repos:</p> +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">project.repositories: + - apache-Mynewt-core +</pre></div> + + +<p><br> </p> +<p>By default, this newly created project uses a single repo called +<code>apache-Mynewt-core</code>. </p> +<p>If you wish to add additional repos, you would add +additional lines to the <code>project.repositories</code> variable like this.</p> +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">project.repositories: + - apache-Mynewt-core + - another_repo_named_x +</pre></div> + + +<p><br></p> +<h3 id="repo-descriptors">Repo Descriptors<a class="headerlink" href="#repo-descriptors" title="Permanent link">¶</a></h3> +<p>In addition to the repo name, the <code>project.yml</code> file must also contain +a repo descriptor for each repository you include that gives <code>newt</code> +information on obtaining the repo.</p> +<p>In the same <code>myproj</code> above you will see the following repo descriptor.</p> +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">repository.apache-Mynewt-core: + type: github + vers: 0-latest + user: apache + repo: incubator-mynewt-core +</pre></div> + + +<p>A repo descriptor starts with <code>repository.<name>.</code>. In this example, the +descriptor specifies the information for the <code>apache-Mynewt-core</code>.</p> +<p><br></p> +<p>The fields within the descriptor have the following definitions:</p> +<ul> +<li> +<p><strong>type</strong> -- The type of code storage the repo uses. The current version +of <code>newt</code> only supports github. Future versions may support generic git or other +code storage mechanisms.</p> +</li> +<li> +<p><strong>vers</strong> -- The version of the repo to use for your project. A source +code repository contains many versions of the source. This field is used to +specify the one to use for this project. See the section on versions below +for a detailed description of the format of this field.</p> +</li> +<li> +<p><strong>user</strong> -- The username for the repo. On github, this is the name +after <code>github.com</code> in the repo path. Consider the repository +<code>https://github.com/apache/incubator-mynewt-core</code>. It has username <code>apache</code>. </p> +</li> +<li> +<p><strong>repo</strong> -- The name of the repo. On github, this is the name after +the username described above. Consider the repository +<code>https://github.com/apache/incubator-mynewt-core</code>. It has username +<code>incubator-mynewt-core</code>. This is a path to the source control +and should not be confused with the name of the repo that you used in the +<code>repository.<name></code> declaration above. That name is contained elsewhere +within the repo. See Below.</p> +</li> +</ul> +<p><br></p> +<h3 id="adding-existing-repos-to-my-project">Adding Existing Repos to my Project<a class="headerlink" href="#adding-existing-repos-to-my-project" title="Permanent link">¶</a></h3> +<p>To add a new repo to your project, you have to complete two steps.</p> +<ul> +<li> +<p>Edit the <code>project.yml</code> file and add a new repo descriptor. The previous +section includes information on the field required in your repo descriptor.</p> +</li> +<li> +<p>Edit the <code>project/yml</code> file and add a new line to the <code>project.repositories</code> +variable with the name of the repo you are adding. </p> +</li> +</ul> +<p>An example if a <code>project.yml</code> file with two repositories is shown below:</p> +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">project.name: "my_project" + +project.repositories: + - apache-Mynewt-core + - Mynewt_arduino_zero + +# Use github's distribution mechanism for core ASF libraries. +# This provides mirroring automatically for us. +# +repository.apache-Mynewt-core: + type: github + vers: 0-latest + user: apache + repo: incubator-mynewt-core + +# a special repo to hold hardware specific stuff for arduino zero +repository.Mynewt_arduino_zero: + type: github + vers: 0-latest + user: runtimeinc + repo: Mynewt_arduino_zero +</pre></div> + + +<p><br></p> +<h3 id="what-version-of-the-repo-to-use">What Version of the Repo to use<a class="headerlink" href="#what-version-of-the-repo-to-use" title="Permanent link">¶</a></h3> +<p>Mynewt repos are version-ed artifacts. They are stored in source control +systems like github. The repo descriptor in your <code>project.yml</code> file must +specify the version of the repo you will accept into your project.</p> +<p>For now, we are at the beginnings of Mynewt. For testing and evaluation +please use <code>0-latest</code> in the <code>vers</code> field in your repo descriptor.</p> +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> vers:0-latest +</pre></div> + + +<p>See below for a description of the version system.</p> +<p><br></p> +<h3 id="what-is-in-a-repo">What is in a Repo<a class="headerlink" href="#what-is-in-a-repo" title="Permanent link">¶</a></h3> +<p>A repo is a collection of Mynewt packages organized in a specific +way and stored in one of the supported code storage methods described above. </p> +<p>A repo is a Mynewt project with an additional file <code>repository.yml</code> +which describes the repo for use by <code>newt</code> (and humans browsing them).</p> +<p>There is one key consideration for this <code>repository.yml</code> file. The +<code>repository.yml</code> file only lives in the master branch of the git +repository. <code>Newt</code> will always fetch this file from the master branch and then +use that to resolve the actual branch required depending on the version +specified in the project. Special care should be taken to ensure that this +file exists only in the master branch.</p> +<p>Here is the <code>repository.yml</code> file from the apache-Mynewt-core:</p> +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">repo.name: apache-mynewt-core +repo.versions: + "0.7.9": "Mynewt_0_8_0_b2_tag" + "0-latest": "0.7.9" + "0.8-latest": "0.7.9" +</pre></div> + + +<p><br></p> +<p>It contains the following:</p> +<ul> +<li><strong>repo.name</strong> The external name that is used to include the library in +your <code>project.yml</code> file. This is the name you in include in the <code>project.repositories</code> variable when adding this repository to your project.</li> +<li><strong>repo.versions</strong> A description of what versions to give the user depending +on the settings in their <code>project.yml</code> file. See below for a thorough description +on versioning. Its a flexible mapping between version numbers and git branches.</li> +</ul> +<p><br></p> +<h3 id="repo-version">Repo Version<a class="headerlink" href="#repo-version" title="Permanent link">¶</a></h3> +<p>The version field argument in your <code>project.yml</code> file has the following format:</p> +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><major_num>.<minor_num>.<revision_num> +</pre></div> + + +<p>or</p> +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><major_num>.<minor_num>-<stability string> +</pre></div> + + +<p>or </p> +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><major_num>-<stability string> +</pre></div> + + +<p><br></p> +<p>The stability string can be one of 3 pre-defined stability values.</p> +<ol> +<li>stable -- A stable release version of the repository</li> +<li>dev -- A development version from the repository</li> +<li>latest -- The latest from the repository</li> +</ol> +<p>In your <code>project.yml</code> file you can specify different combinations of +the version number and stability value. For example:</p> +<ul> +<li><code>0-latest</code> -- The latest version with major number 0</li> +<li><code>1.2-stable</code> -- The latest stable version with major and minor number 1.2</li> +<li><code>1.2-dev</code> -- The development version from 1.2</li> +<li><code>1.1.1</code> -- a specific version 1.1.1</li> +</ul> +<p>You cannot specify a stability string with a fully numbered version, e.g.</p> +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">1.2.8-stable +</pre></div> + + +<p><br></p> +<p>A <code>repository.yml</code> file contains information to match this version request +into a git branch to fetch for your project.</p> +<p>Its up to the repository maintainer to map these to branches of the +repository. For example, let's say in a fictitious repository the following are +defined.</p> +<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">repo.versions: + "0.8.0": "xxx_branch_0_8_0" + "1.0.0": "xxx_branch_1_0_0" + "1.0.2": "xxx_branch_1_0_2" + "1.1.1": "xxx_branch_1_1_0" + "1.1.2": "xxx_branch_1_1_2" + "1.2.0": "xxx_branch_1_2_0" + "1.2.1": "xxx_branch_1_2_1" + "1.2-dev": "1.2.1" + "1-dev": "1.2-dev" + "1.2-stable": "1.2.0" + "0-latest": "0.8.0" + "1-latest": "1-dev" + .... +</pre></div> + + +<p>When the <code>project.yml</code> file asks for <code>1.2-stable</code> its resolved to version +<code>1.2.0</code> (perhaps <code>1.2.1</code> is not stable yet), which resolves to a specific +branch <code>xxx_branch_1_2_0</code>. This is the branch that <code>newt</code> fetches into +your project.</p> +<p><br></p> +<h3 id="how-to-find-out-what-repos-are-available-for-mynewt-components">How to find out what Repos are available for Mynewt components<a class="headerlink" href="#how-to-find-out-what-repos-are-available-for-mynewt-components" title="Permanent link">¶</a></h3> +<p>Currently, there is no <code>newt</code> command to locate/search Mynewt package +repositories. However, since the <code>newt</code> tool supports only github, +searching github by keyword is a satisfactory option until a search +tool is created.</p> +<p>When searching github, recall that a Mynewt repository must +have a <code>repository.yml</code> file in its root directory. If you don't see +that file, it's not a Mynewt repository and can't be included in your +project via the newt tool. </p> +<p>Once you find a repository, the github URL and <code>repository.yml</code> file +should give you all the information to add it to your <code>project.yml</code> file.</p> +<p><br></p> + + <div class="row"> + <footer> + <div class="row"> + <div class="col-md-12"> + + <p class="copyright">Copyright © 2015 The Apache Software Foundation, Licensed under the Apache License, Version 2.0 Apache and the Apache feather logo are trademarks of The Apache Software Foundation.<br>The Apache Software Foundation Apache Incubator</p> + + </div> + </div> + <div class="copyright-logos"> + <div class="row"> + <div class="col-xs-6 text-right"> + <img src="/img/apache-feather.png" alt="Apache" title="Apache"> + </div> + <div class="col-xs-6 text-left"> + <img src="/img/apache-logo.png" alt="Apache Incubator" title="Apache Incubator"> + </div> + </div> + </div> + <div class="row"> + <div class="col-md-12"> + <small class="footnote"> + MyNewt is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. + </small> + </div> + </div> +</footer> + </div> + </div> + </div> + + + </div> + + <script src="../../../js/jquery-1.10.2.min.js"></script> + <script src="../../../js/bootstrap-3.0.3.min.js"></script> + <script src="../../../js/highlight.pack.js"></script> + <script src="../../../js/base.js"></script> + <script src="../../../js/custom.js"></script> + + </body> +</html> \ No newline at end of file http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bb4af1c8/os/tutorials/air_quality_sensor/index.html ---------------------------------------------------------------------- diff --git a/os/tutorials/air_quality_sensor/index.html b/os/tutorials/air_quality_sensor/index.html index e2c13d3..97fadc1 100644 --- a/os/tutorials/air_quality_sensor/index.html +++ b/os/tutorials/air_quality_sensor/index.html @@ -300,6 +300,16 @@ + + + + <li> + <a href="../add_repos/">Additional Repositories</a> + </li> + + + + </ul> </li> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bb4af1c8/os/tutorials/arduino_zero/index.html ---------------------------------------------------------------------- diff --git a/os/tutorials/arduino_zero/index.html b/os/tutorials/arduino_zero/index.html index cd0bedd..efe4eda 100644 --- a/os/tutorials/arduino_zero/index.html +++ b/os/tutorials/arduino_zero/index.html @@ -300,6 +300,16 @@ + + + + <li> + <a href="../add_repos/">Additional Repositories</a> + </li> + + + + </ul> </li> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bb4af1c8/os/tutorials/how_to_edit_docs/index.html ---------------------------------------------------------------------- diff --git a/os/tutorials/how_to_edit_docs/index.html b/os/tutorials/how_to_edit_docs/index.html index 67fe4b3..7aa464e 100644 --- a/os/tutorials/how_to_edit_docs/index.html +++ b/os/tutorials/how_to_edit_docs/index.html @@ -300,6 +300,16 @@ + + + + <li> + <a href="../add_repos/">Additional Repositories</a> + </li> + + + + </ul> </li> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bb4af1c8/os/tutorials/nRF52/index.html ---------------------------------------------------------------------- diff --git a/os/tutorials/nRF52/index.html b/os/tutorials/nRF52/index.html index f072ce8..85f9cea 100644 --- a/os/tutorials/nRF52/index.html +++ b/os/tutorials/nRF52/index.html @@ -300,6 +300,16 @@ + + + + <li> + <a href="../add_repos/">Additional Repositories</a> + </li> + + + + </ul> </li> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bb4af1c8/os/tutorials/olimex/index.html ---------------------------------------------------------------------- diff --git a/os/tutorials/olimex/index.html b/os/tutorials/olimex/index.html index 00e7c9e..4d9d799 100644 --- a/os/tutorials/olimex/index.html +++ b/os/tutorials/olimex/index.html @@ -300,6 +300,16 @@ + + + + <li> + <a href="../add_repos/">Additional Repositories</a> + </li> + + + + </ul> </li> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bb4af1c8/os/tutorials/tutorials/index.html ---------------------------------------------------------------------- diff --git a/os/tutorials/tutorials/index.html b/os/tutorials/tutorials/index.html index 356a267..bd156f4 100644 --- a/os/tutorials/tutorials/index.html +++ b/os/tutorials/tutorials/index.html @@ -300,6 +300,16 @@ + + + + <li> + <a href="../add_repos/">Additional Repositories</a> + </li> + + + + </ul> </li> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bb4af1c8/os/tutorials/unit_test/index.html ---------------------------------------------------------------------- diff --git a/os/tutorials/unit_test/index.html b/os/tutorials/unit_test/index.html index 142ada5..045a959 100644 --- a/os/tutorials/unit_test/index.html +++ b/os/tutorials/unit_test/index.html @@ -300,6 +300,16 @@ + + + + <li> + <a href="../add_repos/">Additional Repositories</a> + </li> + + + + </ul> </li> http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/bb4af1c8/sitemap.xml ---------------------------------------------------------------------- diff --git a/sitemap.xml b/sitemap.xml index 73c3312..497e91e 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -4,7 +4,7 @@ <url> <loc>http://mynewt.apache.org/</loc> - <lastmod>2016-03-17</lastmod> + <lastmod>2016-03-18</lastmod> <changefreq>daily</changefreq> </url> @@ -12,7 +12,7 @@ <url> <loc>http://mynewt.apache.org/about/</loc> - <lastmod>2016-03-17</lastmod> + <lastmod>2016-03-18</lastmod> <changefreq>daily</changefreq> </url> @@ -20,7 +20,7 @@ <url> <loc>http://mynewt.apache.org/documentation/</loc> - <lastmod>2016-03-17</lastmod> + <lastmod>2016-03-18</lastmod> <changefreq>daily</changefreq> </url> @@ -28,7 +28,7 @@ <url> <loc>http://mynewt.apache.org/download/</loc> - <lastmod>2016-03-17</lastmod> + <lastmod>2016-03-18</lastmod> <changefreq>daily</changefreq> </url> @@ -36,7 +36,7 @@ <url> <loc>http://mynewt.apache.org/community/</loc> - <lastmod>2016-03-17</lastmod> + <lastmod>2016-03-18</lastmod> <changefreq>daily</changefreq> </url> @@ -44,7 +44,7 @@ <url> <loc>http://mynewt.apache.org/events/</loc> - <lastmod>2016-03-17</lastmod> + <lastmod>2016-03-18</lastmod> <changefreq>daily</changefreq> </url> @@ -53,7 +53,7 @@ <url> <loc>http://mynewt.apache.org/os/get_started/introduction/</loc> - <lastmod>2016-03-17</lastmod> + <lastmod>2016-03-18</lastmod> <changefreq>daily</changefreq> </url> @@ -93,7 +93,7 @@ <url> <loc>http://mynewt.apache.org/newt/newt_intro/</loc> - <lastmod>2016-03-17</lastmod> + <lastmod>2016-03-18</lastmod> <changefreq>daily</changefreq> </url> @@ -115,13 +115,13 @@ <url> <loc>http://mynewt.apache.org/newtmgr/overview/</loc> - <lastmod>2016-03-17</lastmod> + <lastmod>2016-03-18</lastmod> <changefreq>daily</changefreq> </url> <url> <loc>http://mynewt.apache.org/newtmgr/installing/</loc> - <lastmod>2016-03-17</lastmod> + <lastmod>2016-03-18</lastmod> <changefreq>daily</changefreq> </url> @@ -143,7 +143,7 @@ <url> <loc>http://mynewt.apache.org/faq/answers/</loc> - <lastmod>2016-03-17</lastmod> + <lastmod>2016-03-18</lastmod> <changefreq>daily</changefreq> </url>
