Package: svn-buildpackage
Version: 0.6.23
Severity: wishlist

Hi,

I'm having a package with a standard svn-buildpackage layout trunk/
tags/ and branches/ with full sources in SVN.
I was wondering how to manage different branches (unstable,
experimental, etc) with this layout and svn-buildpackage.

E.g. svn-upgrade always imports new upstream versions into trunk. That
causes problems if I want to package a new upstream version for
experimental, as I can easily switch back to the unstable branch.

How can I do that with svn-buildpackage? Does svn-buildpackage actually
support such a use case and/or is it just missing documentation?

Something like 
svn-upgrade ../path/to/new/orig.tar.gz --branch experimental
would be helpful, which imports the upstream version in, say
branches/experimental, switches the working copy to this branch and
allows me to work from there.

Cheers,
Michael


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.27-rc8
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages svn-buildpackage depends on:
ii  devscripts                 2.10.38       scripts to make the life of a Debi
ii  file                       4.26-1        Determines file type using "magic"
ii  libsvn-perl                1.5.1dfsg1-1  Perl bindings for Subversion
ii  liburi-perl                1.35.dfsg.1-1 Manipulates and accesses URI strin
ii  perl                       5.10.0-15     Larry Wall's Practical Extraction 
ii  subversion                 1.5.1dfsg1-1  Advanced version control system
ii  unp                        1.0.15        unpack (almost) everything with on
ii  wget                       1.11.4-2      retrieves files from the web

svn-buildpackage recommends no packages.

svn-buildpackage suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to