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

RE: How to handle EXE

From: Bicking, David (HHoldings, IT) <David.Bicking_at_thehartford.com>
Date: 2007-11-06 18:46:19 CET

(converted to ASCII)
________________________________

        From: Unterman Israel [mailto:israelu@elbit.co.il]

        Hi all,

        Each time I compile my project a new 8MB EXE is generated.

        I wouldn't like to commit it to svn each time I make a build,
because 100 commits will become 800 Mbytes.

        But I DO want to commit it SOMETIMES, to have an available EXE
for release versions.

        I tried committing the EXE only when needed, but this way I
always have it listed on the status as modified, which is annoying.

        More annoying is with Tortoise, where I always have a "!" mark
on the project's folder, due to the not-committed exe.

        I'll appreciate your advices about this.

        Thanks

        
--------------------------------------------------------------------

Don't put it in your project that way. create a folder in the
repository that just has release binaries and periodically update them
by copying the built files into the appropriate workspace and
committing. Consider a structure like this:
 
MyProject --> trunk
    |---branches
    |---tags
    |---Release Binaries
 
On the other hand, why do you want to store the binaries at all? Are
they shared DLLs that will be referenced by other projects? I don't
think it is generally a good idea to store the binary result, but
instead tag your source so that the binaries of any version can be built
on demand.
 

--
David
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 6 18:46:49 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.