Skip to content

Commit

Permalink
copied whole robotpkg repository and put it here.
Browse files Browse the repository at this point in the history
  • Loading branch information
janpaulus committed Aug 17, 2010
1 parent ae68b51 commit 1f3f924
Show file tree
Hide file tree
Showing 2,310 changed files with 479,833 additions and 0 deletions.
11 changes: 11 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
distfiles
packages
wip

INDEX
index.html
index-all.html

work

*~
79 changes: 79 additions & 0 deletions Makefile
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
# $LAAS: Makefile 2009/07/28 13:53:36 mallet $
#
# Copyright (c) 2007-2009 LAAS/CNRS
# All rights reserved.
#
# This project includes software developed by the NetBSD Foundation, Inc.
# and its contributors. It is derived from the 'pkgsrc' project
# (http://www.pkgsrc.org).
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
#
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in
# the documentation and/or other materials provided with the
# distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHORS AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
# PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# From $NetBSD: Makefile,v 1.81 2007/02/20 22:46:32 agc Exp $
#
# Anthony Mallet on Tue May 22 2007


# This is the top-level Makefile of robotpkg. It contains a list of the
# categories of packages, as well as some targets that operate on the
# whole robotpkg system.
#
# User-settable variables:
#
# SPECIFIC_PKGS
# (See mk/defaults/mk.conf)
#
# See also:
# mk/misc/toplevel.mk
#

SUBDIR+= architecture
SUBDIR+= archivers
SUBDIR+= audio
SUBDIR+= cross
SUBDIR+= devel
SUBDIR+= doc
SUBDIR+= graphics
SUBDIR+= hardware
SUBDIR+= image
SUBDIR+= interfaces
SUBDIR+= knowledge
SUBDIR+= lang
SUBDIR+= localization
SUBDIR+= manipulation
SUBDIR+= mapping
SUBDIR+= math
SUBDIR+= meta-pkgs
SUBDIR+= motion
SUBDIR+= net
SUBDIR+= optimization
SUBDIR+= path
SUBDIR+= pkgtools
SUBDIR+= robots
SUBDIR+= scripts
SUBDIR+= shell
SUBDIR+= sysutils
SUBDIR+= www

include mk/robotpkg.subdir.mk
3 changes: 3 additions & 0 deletions README
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
Please see README.txt README.html for information.

PLEASE NOTE: the documentation is very incomplete at the moment. Sorry.
85 changes: 85 additions & 0 deletions README-release
Original file line number Diff line number Diff line change
@@ -0,0 +1,85 @@
How to release a new version of a package
-----------------------------------------

autotools packages
------------------
In the package
- be sure that your working version is up to date.
- in ChangeLog: add missing commit messages and notify new release
- in configure.ac: upgrade the version number
- in configure.ac or package.pc.in: upgrade dependency versions
- cd build; make to check that package compiles
- cd build; make dist
- make sure the archive is readable (chmod a+r archivename.tar.gz)
- look into robotpkg package Makefile,
- if MASTER_SITES=${MASTER_SITE_JRL}
ftp softs.laas.fr, login jrl
> put nameofthepackage-x.y.tar.gz
- if MASTER_SITES= ${MASTER_SITE_OPENROBOTS:=directory/}
scp nameofthepackage-x.y.tar.gz softs.laas.fr://www/htdocs/openrobots/distfiles/directory/.

In openrobots/robotpkg/.../package
- update Makefile with new version number
- make mdi
- make install
- make print-PLIST builds the list of files and directories to be destroyed when deinstalling.
- edit PLIST.guess and remove irrelevant lines.
- mv PLIST.guess PLIST
- make clean to remove build directory.
- commit the modifs.
- prefix commit message by [category/package],
- insert list of changes from ChangeLog in commit body message.

In the package
- commit and push
- add a tag.
- git-tag -m "release x.y" x.y
- increment version number as x.y.99
- git commit
- git-push --tags

cmake packages
--------------

In the package
- be sure that your working version is up to date.
- make a temporary branch: git checkout -b release-x.y
- in ChangeLog: add missing commit messages and notify new release
- in CMakeLists.txt: upgrade the version number
- in CMakeLists.txt: upgrade dependency versions
- cd build; rm -rf *; cmake -DCMAKE_INSTALL_PREFIX=/tmp ..; make install to check that package compiles
- git commit -a
- git archive --format=tar --prefix=nameofthepackage-x.y/ HEAD | gzip > nameofthepackage-x.y.tar.gz
- make sure the archive is readable (chmod a+r nameofthepackage-x.y.tar.gz)
- look into robotpkg package Makefile,
- if MASTER_SITES=${MASTER_SITE_JRL}
ftp softs.laas.fr, login jrl
> put nameofthepackage-x.y.tar.gz
- if MASTER_SITES= ${MASTER_SITE_OPENROBOTS:=directory/}
scp nameofthepackage-x.y.tar.gz softs.laas.fr://www/htdocs/openrobots/distfiles/directory/.

In openrobots/robotpkg/.../package
- update Makefile with new version number
- make mdi
- make install
- make print-PLIST builds the list of files and directories to be destroyed when deinstalling.
- edit PLIST.guess and remove irrelevant lines.
- mv PLIST.guess PLIST
- make clean to remove build directory.
- commit the modifs.
- prefix commit message by [category/package],
- insert list of changes from ChangeLog in commit body message.

In the package
- add a tag.
- git-tag -m "release x.y" x.y
- merge branch release-x.y into master
- increment version number as x.y.99
- git commit
- git-push --tags

Important
---------

It is recommended to do one commit by package upgraded. It is then easier to trace
back the changes in each package.
Loading

0 comments on commit 1f3f924

Please sign in to comment.