Tickets :: Comment on [#5284] Move to subversion for Horde code repository

* Your Email Address
* Spam protection	Enter the letters below: .__.._.. .. , __. \| \| \| \|\/\| \./ (__ \|__\_\|_\| \| \| .__)
Comment	>> But that would meen that anybody checking out the horde module from > >> FW_3 would get all apps checked out too, correct? > > > > Right - I don't think that's so bad. If they want exact installs they > can use tarballs, and the world of FW_3 apps isn't as huge as HEAD > apps. > > > >> After taking a look at the current SVN repository, I changed my mind > >> and think we should setup separate modules for each Horde app. Having > >> all tags and branches for all horde modules ever in branches/ and > >> tags/ looks really cluttered. I think it's worth not being able to > >> svn mv between horde modules for the benefit of a cleaner layout. > > > > We could still svn mv/copy between them, unless we really made them > completely separate repositories. There is nothing hardcoded in > subversion about trunk/tags/etc - it's just a convention. We could to > a top-level list of modules with their own trunk, tags, branches > dirs, or we could do subdirs inside the /tags and /branches dirs just > like we have inside /trunk.
Attachment
Watch this ticket