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

Re: How to avoid cluttering the svn repository with several versions of compiled files

From: Andreas Schweigstill <andreas_at_schweigstill.de>
Date: Thu, 14 May 2009 16:40:46 +0200

Hello!

Andy Levy schrieb:
> Aside from space
> efficiencies (which may not even be realized, due these being binary
> files), there's not much to be gained by putting releases into
> Subversion instead of a decently-structured archive directory on a
> server.

But this requires access to a file server which is not always given.
For some customer projects I only have a VPN connection to the SVN
server.

And I think I make really a lot of sense to keep source and binaries
for such purposes in a common location. File server locations don't
allow/force the user to put a message directly onto the stored files.
It would be possible to create files like README.txt or RELEASENOTES.txt
but they don't "stick" to the generated binaries.

Regards
Andreas Schweigstill

-- 
BITTE BEACHTEN SIE UNSERE NEUE TELEFONNUMMER!
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 53035-435, Fax: (+49) 431 53035-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2258217
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-14 16:41:57 CEST

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.