Re: storing software releases in Subversion - how?

Ivan-Assen Ivanov wrote:
> Once in a couple of days we make new "builds" of our software. A
> build is a directory tree with files numbering in the 1000s. ...
>
> Is there a magical combination of commands and switches which will do
> what I want?
>

Pep wrote:
>
> It sound likes you need to read the section of the manual on
> branches. ....

Jeroen Coumans wrote:
> It seems you need to use Subversion for all your developers activity
> (modify, add, delete), instead of just releases. Only then can you
> extract the information which you require.
>
no, if I understand him right, he talkes about builds,
i.e. generated binaries. He wants to maintain diffs of
them?

Assen,

it seems, that your problem is closely related to the
"vendor brances" where you check in a series of sourcecode
of third party libraries. You can than create a diff on
the vendor branch and patch this onto your own (probably
modified) version of the third party library on main thunk.

See the book, Chapter 7 (Advanced Topics/Vendor Branches).
There is a reference to a script svn_load_dirs.pl
If I understand right, this does what you wants.

-- 
Hope this helps,
Regards,
Hermann
---------------------------------------------------------------
Hermann Voßeler
Baader Wertpapierhandelsbank AG
Weihenstephaner Straße 4
D-85716 Unterschleißheim
eMail: hermann.vosseler@baaderbank.de
Internet: www.baaderbank.de
---------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org