GNU/Linux
•
xterm
•
bash
696 views
-
carry out the step of Preparing_the_Upstream_Repository. Be aware that all
package.xmlin your repository need to be properly set up (license suggest as MIT, author(s) and maintainer entered), and that they all need to be at the same version number (0.0.0looks like a good starting point). - create a release repository with the same name as the repository you plan to release in the github organisation strands-project-releases (ask @marc-hanheide for permissions or to do it for you). The repository will be automatically populated and is referred to as RELEASE repository url (see https://github.com/strands-project-releases/mongodb_store.git, for instance)
-
use bloom to create the release:
This will interactively ask some information from you:bloom-release --rosdistro hydro --track hydro repository_name --edit -
when first asked for the Release repository url, enter the git URL for the just created repo (e.g.
https://github.com/strands-project-releases/mongodb_store.git) -
when asked for Repository Name, please enter the name of your repository, e.g.
mongodb_store -
when asked for Upstream Repository URI, please enter the path to your upstream repository, that is the one hosted in the
strands-projectgithub organisation that you commit to, e.g.https://github.com/strands-project/mongodb_store.git -
when asked for ROS Distro, say
hydro(orindigoif that is eventually supported by STRANDS) - when asked Would you like to add documentation information for this repository?, say no
-
when asked Would you like to add source information for this repository?, say yes, and subsequently tner the URL to your active development repository (usually the same as the upstream repo, so in our example:
https://github.com/strands-project/mongodb_store.gitagain - answer all other questions just by hitting return (accepting the defaults)
You should see bloom creating a lot of stuff for you (debian configurations and other stuff). At the end, bloom should automatically open a pull request against STRANDS’ own distribution.yaml with your package added to this. The STRANDS software management team will have a look at this and eventually accept it. Then the build farm will create debian packages for you (and package maintainers will receive emails automatically if the build fails) which will then be available for everybody to use.