On Fri, 4 Sep 2009, Heikki Johannes Junes wrote:
> In stead of
>
> (1)
> trunk/
> branches/notation_tool_2/
> tags/project_packager_rewrite/
>
> we have
>
> (2)
> trunk/rosegarden/
> branches/notation_tool_2/
> tags/project_packager_rewrite/
>
> If we would strictly obey the trunk-branches-tags pattern, we should have
>
> (3)
> trunk/rosegarden/
> branches/notation_tool_2/rosegarden/
> branches/project_packager_rewrite/rosegarden/
>
> In my opinion, we should choose pattern (1).
Is there any reason against (3)?
In order to keep the rosegarden directory well structured and compile
time low, I could imagine to have some third party software (maybe for
importing other formats like musicxml) in a parallel directory and only
checkin prebuilt libs in rosegarden itself.
So in trunk nothing has to be changed and maintainer of new branches
should keep in mind to use one more directory level. Instead of using
svn copy https://<user>@<sf-host>/svnroot/rosegarden/trunk/rosegarden \
https://<user>@<sf-host>/svnroot/rosegarden/branches/<my_branch>
it would be:
svn copy https://<user>@<sf-host>/svnroot/rosegarden/trunk \
https://<user>@<sf-host>/svnroot/rosegarden/branches/<my_branch>
or in case of further parallel directories:
svn copy --parents https://<user>@<sf-host>/svnroot/rosegarden/trunk/rosegarden
\
https://<user>@<sf-host>/svnroot/rosegarden/branches/<my_branch>/rosegarden
(I hope despite the automatic word wrap it is still clear what I mean :-))
Thorsten
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
