[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: import --force?

From: Matt Sickler <crazyfordynamite_at_gmail.com>
Date: 2007-03-23 13:14:52 CET

sounds like someone is using a source code control system as a binary
distribution system.
svn is used to version source code, not give an easy way to distribute
compiled binaries or libraries
you wouldnt use a fork to eat soup now would you?

On 3/23/07, André Pönitz <andre@wasy.de> wrote:
> Hi all.
> I am currently trying to build a repository consisting of
> 'redistributables' of several of our projects.
> The idea is that a couple of projects create 'something'
> (usually the stuff that's copied around on 'make install').
> This 'something' should be collected in an svn project,
> so that everybody can get said 'something' via 'svn export'
> without having to build it by himself.
> I have a working solution for that, but that's Not Nice(tm).
> I use:
> #!/bin/bash
> BuildRoot=...
> Repo=https://svn/repository/x
> for i in \
> {x86,x64}/bin8/foo.dll \
> {x86,x64}/dbg8/food10.dll \
> include/foo.h
> do
> echo "Updating: $i"
> svn remove --non-interactive --quiet -m "Remove $i" "$Repo/$i"
> svn import --non-interactive --quiet -m "Update $i" "$BuildRoot/$i"
> "$Repo/$i"
> done
> I.e. for each file I wich to redistribute I run svn remove and
> svn import, so for n files I get 2*n svn revisions, which gets
> awful if I distribute a few hundred files.
> An improvement would be to create a temporary directory linking
> in all the 'interesting' files and use svn import's recursive
> capabilities. However, that stll leaves the 'remove' step,
> which in turn seems to be needed as import refuses to overwrite
> an already existing file in the repo.
> The 'ideal' solution would be some kind of '--force' flag
> for svn import that would ignore that fact, but that does not
> seem to be available (at least not wih 1.2.0)
> So the question: Does anybody have an idea how to improve this
> setup?
> Andre'
> PS: I could, of course, check out some working copy, copy the new
> stuff over and run an ordinary commit, but that's not too nice either
> as it occupies local storage that's not exactly needed.
> I could also rsync the stuff to a wc checked out locally on the
> server and commit from there (and I will probably do that if
> no other idea crops up). Not too nice, either, even if the wc
> on the server won't hurt that much...
> --
> André Pönitz, Software Developer
> WASY GmbH, Institute for Water Resources Planning and System
> Research, Waltersdorfer Straße 105, 12526 Berlin, Germany
> Register Court: Amtsgericht Charlottenburg, HRB 36263
> Management: H.-J. G. Diersch, S. Kaden, I. Michels
> Phone: +49 30 67 99 98-0; Fax: +49 30 67 99 98-99
> Web: www.wasy.de, E-Mail: andre@wasy.de
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 23 13:15:23 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.