Hi, Florian Ragwitz wrote: > On Sun, Jul 31, 2005 at 07:03:14AM -0400, Yaroslav Halchenko wrote: > >>On Sun, Jul 31, 2005 at 09:59:04AM +0000, W. Borgert wrote: >> >>>- How do I have to arrange the repository, so that >> >>better use arrangement which svn-buildpackage creates >>branches trunk tags upstream build-area and tarballs >> >> >>> under pkg-greetings/hello/tags/1.0-1/? Or do I have to put >>> the upstream under pkg-greetings/hello/branches/upstream/1.0/? >> >>svn-inject and consequently svn-upgrade does it for you >> >>[...] >> >>borrowed from a nice minimalistic HOWTO >>http://workaround.org/moin/SvnBuildpackage > > > This howto says that I should use -c 2 to get tarballs/ created. Why is > that necessary? The tarball also could be created from > ../branches/upstream/current (relative to trunk (either in the local fs > or in the svn repository). > -c 2 makes the layout in svn. But you can have only the debian directory under version control, have a tarballs directory and have set the property mergeWithUpstream in svn.
> I don't want to have all revisions of the package that ever existed on > my filesystem. Is it possible to make svn-buildpackage create the > tarballs on build-time? > AFAIK it isn't possible. > > Regards, > Flo > Regards, Matthijs Mohlmann
signature.asc
Description: OpenPGP digital signature
