> Thinking more about this, though, how about leaving these in > spec-files and creating a new repo for GNOME? (Is there a way > to do that without losing svn history?) So we would have > spec-files-gnome and spec-files.
I don't like doing anything this disruptive right now, but it would make sense to rename it spec-files-gnome when we have migrated the non-gnome stuff out. How about if we name the new repos "spec-files-other" and plan to rename spec-files to spec-files-gnome later? The python, etc subdirs seem OK, but the paths might be getting a bit long, eg .../spec-files-other/trunk/core/libs/graphics/SUNW*.spec so again I'd prefer to just have the core/stable/experimental dirs. So, my proposal now is: - leave spec-files as it is, but plan to rename it to spec-files-gnome once we have moved all the non-gnome stuff out of it. - create a new repos, spec-files-other in which each branch has the following subdirs: core stable experimental - initially, we would plan to integrate the pkgs in core into Nevada Any objections? - Dermot > > Another thing I was thinking about was how to organise the new > repository. If we are going to have lots of new spec files, > we really should sort things into subdirs rather than > dumping everything in the root dir. So maybe we should have > something like > > spec-files/python/ -- python itself and python modules > spec-files/libs/graphics -- png, tiff, jpg, etc. > libs/codecs -- speex, theora, etc > spec-files/perl -- perl modules > spec-files/apps/internet -- xchat, etc > spec-files/apps/graphics -- inkscape, etc > > Laca > >
