[med-svn] [Debian Wiki] Update of "DebianMed" by SteffenMoeller

[Debian Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.

The "DebianMed" page has been changed by SteffenMoeller:
http://wiki.debian.org/DebianMed?action=diff&rev1=84&rev2=85

  svn-buildpackage --svn-tag-only --svn-noautodch}}}
   which avoids the changelog getting tagged UNRELEASED.
  === Whenever preparing new packages, please: ===
-  a. use patches and [[dpatch]] or [[quilt]], so there is no or little need to tamper with upstream's files directly.
+  a. use [[quilt]] as a patch system, so there is no or little need to tamper with upstream's files directly and handling of the patches is performed automatically with a file 'debian/source' reading '3.0 (quilt)'.
   a. Upload the new package to the repository: New packages are first submitted to the Alioth svn '''after''' that package was first successfully packaged through dpkg-buildpackage
   {{{
  aliothID="yourid-guest" # adapt to what your ID is
  svnrepos=svn+ssh://${aliothID}@svn.debian.org/svn/debian-med/trunk/packages
  svn-inject -v -o package.dsc $svnrepos}}}
+  a.  If 'svn-inject' does not work or if there is no package available, yet, then follow the instructions of the next section.
   a.  a. Check out the source from svn. Change directory to the folder containing the debian'' directory and the '''merge''' mode of subversion. From the man page:         "With this method, only the debian directory (and maybe some other modified files)  are  stored  in the  repository. At  build  time,  the  contents of the svn trunk are copied to the extracted tarball contents (and can  overwrite  parts  of it). To choose  this working model, set the svn property mergeWithUpstream on  the  Debian  directory: {{{svn  propset  mergeWithUpstream  1 debian}}}" ''
   a. If svn-b'' (see above aliases) does not find the orig.tar.gz, then help with with setting the origDir. For best compatibility with the [[uscan]] auto-downloader from the [[devscripts]] package, it is suggested to specify the folder to folders above your package's debian folder. From within the trunk folder execute: {{{echo "origDir=.." >> .svn/deb-layout}}}. To retrieve the latest version of the package, if the debian/watch file is correctly set, then execute "uscan" as usual. ''
+ 
+ <<anchor(manually)>>
+ === Preparing new packages manually ===
+ 
+  a. Check out debian-med/trunk, cd to debian-med/trunk/packages
+  a. Create new project folder with {{{
+ svn mkdir projectname
+ svn mkdir projectname/trunk
+ }}}
+  a. Put orig.tar.gz in place {{{
+ mv some_version.orig.tar.gz projectname
+ }}}
+  a. Inform svn-buildpackage about the location of the orig.tar.gz {{{
+ echo "origDir=.." > projectname/trunk/.svn/deb-layout
+ }}}
+  a. Untar source tree for development {{{
+ cd projectname
+ tar xzvf some_version.orig.tar.gz
+ cd some-version # entering the unpackaged source tree
+ if [ ! -d debian ]; then dh_make ; fi
+ mv debian ../trunk
+ ln -s ../trunk/debian .
+ # continue development
+ fakeroot ./debian/rules binary
+ # until it works, finally
+ cd ..
+ }}}
+  a. debian directory is the only thing that is stored in svn, to be merged with upstream {{{
+ svn propset mergeWithUpstream 1 trunk/debian
+ }}}
+  a. see if things can be compiled via svn-buildpackage {{{
+ cd trunk
+ svn-buildpackage -rfakeroot -uc -us
+ }}}
+  a. check build {{{
+ lintian ../build-area/*changes
+ }}}
+ 
+ 
  
  == References ==