[Pkg-gourmet-changes] gourmet/debian README.Maintainer,NONE,1.1
seanius at haydn.debian.org
seanius at haydn.debian.org
Tue Sep 20 15:05:11 UTC 2005
- Previous message: [Pkg-gourmet-changes] gourmet CHANGES, 1.2, 1.3 FAQ, 1.1.1.1,
1.2 MANIFEST, 1.2, 1.3 PKG-INFO, 1.2, 1.3 setup.py, 1.1.1.1, 1.2
- Next message: [Pkg-gourmet-changes] gourmet/i18n/ca/LC_MESSAGES gourmet.mo,
1.1.1.1, 1.2
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Update of /cvsroot/pkg-gourmet/gourmet/debian
In directory haydn:/org/alioth.debian.org/chroot/home/users/seanius/tmp/cvs-serv30504/debian
Added Files:
README.Maintainer
Log Message:
update for upstream source to 0.8.6.5.1
--- NEW FILE: README.Maintainer ---
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# The following information is documentation for how we currently
# manage and update the gourmet source package in debian.
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# Currently, gourmet is hosted in a CVS repository on alioth:
#
# cvs.alioth.debian.org:/cvsroot/pkg-gourmet
#
# managing the existing package
#
# while we're using CVS, the entire source tree has been ported into the
# repository so that we can use some utility like cvs-buildpackage for
# managing tags, branches, revisions, etc. to build a package with
# cvs-buildpackage, perform the following steps:
# checkout/updated a current version of the CVS tree. i keep mine in
# ${HOME}/debian/gourmet/sid, where "sid" contians the entire source
# tree (i.e.: sid/debian/changelog).
#
# preparing a new upstream version
#
# there are two complications to preparing new upstream versions:
#
# 1 - the new upstream version may bring in new files, leave old files
# behind, wrt CVS (this wouldn't be an issue if we only had to track
# ./debian, like we could in svn)
# 2 - upstream ships their own ./debian dir so care must be taken to to
# "cross-polinate" the two directories.
#
# so, this in mind, this is the procedure:
# - download the latest upstream tarball. keep a copy of if somewhere outside
# your working area in case you accidentally nuke it.
# - untar the tarball
tar xvfz gourmet-x.y.z.tar.gz
# - copy over the files, skipping everything in ./debian and deleting
# files that no longer exist. you might want to test this first :)
rsync -nav --delete --exclude debian --exclude CVS gourmet-x.y.z/ sid/ | less
# when you're happy with what you see:
rsync -nav --delete --exclude debian --exclude CVS gourmet-x.y.z/ sid/
# - view the differences in the repository, looking specifically for
# added and removed files
cvs diff -u | grep -E '^(cvs diff: cannot find)|\? '
# or alternatively, do a cvs commit, and then diff to see what's
# been added/removed. in any case, make sure you add all new files
# and remove all obsolete files.
# - make whatever changes are necessary in ./debian (changelog, rules, etc)
- Previous message: [Pkg-gourmet-changes] gourmet CHANGES, 1.2, 1.3 FAQ, 1.1.1.1,
1.2 MANIFEST, 1.2, 1.3 PKG-INFO, 1.2, 1.3 setup.py, 1.1.1.1, 1.2
- Next message: [Pkg-gourmet-changes] gourmet/i18n/ca/LC_MESSAGES gourmet.mo,
1.1.1.1, 1.2
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Pkg-gourmet-changes
mailing list