Subversion repository structure (was: trunk/kdeedu/klettres)

mETz mETz81 at web.de
Sat Feb 19 20:20:05 GMT 2005


On Samstag Februar 19 2005 21:10, Thiago Macieira wrote:
> Aaron J. Seigo wrote:
> >as long as the new structure was well documented (e.g. on
> > developer.kde.org), i'd personally be fine with enduring a month or two
> > of discomfort due to things not being where i'm used to if that meant
> > the repository would be easier to use going forward.
>
> Actually, what I would propose would be:
> - Move the main KDE modules into a subdir in trunk called "KDE"
> - Dismantle the kdeextragear-* subdirs and let each app live on their own
> dir, inside /trunk

would look a bit messy in / then. Also you would "hide" kde itself in KDE and 
present all other apps in /, that's weird.

> [...]
> Or, then, another possibility:
> - Move the main KDE modules into a subdir in trunk called "KDE"
> - Dismantle the multiple kdeextragear-* subdirs, but move them to one
> master dir called /trunk/extragear
> - Same for kdereview and kdeplayground
>
> Why? Think of branching:
> svn cp trunk/KDE branches/KDE/4.0
> svn cp trunk/kdevelop work/kdevelop-support-svn
> svn cp trunk/amarok releases/amarok/1.3.1
>
> The only loose end would be kde-common/admin.
>
> [...]
> Any thoughts?

I'd be in favor of your second possibility :)

Bye, Stefan aka mETz




More information about the kde-core-devel mailing list