Hi, > > Cool. I didn't realize that rosegarden4 was orphaned at all. > > I am interested in getting this thing updated in Debian. > > > > I prefer working out of a svn/cvs repos rather than shifting around > > whole packages. > > I ran svn-inject, and my package is here: > > svn://svn.vireo.org/rosegarden/rosegarden4
Humph, I was hoping that you'd inject it to somewhere like the demudi repos so that I can have read/write access. Free, are you fine with the idea of using http://svn.debian.org/wsvn/demudi for rosegarden as well? > > I've looked at rosegarden4 sources and it blew my mind away; it's > > using 'scons' for building, and decided to throw away > > autoconf/automake/Makefile set up ? > > yeah. Don't konw what the motivation was there. The rosegarden-devel > list is already talking about possibly moving from scons to something > else: > > http://sourceforge.net/mailarchive/forum.php?thread_id=9886891&forum_id=271 Yikes. > > How did you handle the 'rosegarden' -> 'rosegarden4' rename that was > > probably Debian-local, did you just throw it away? > > > > In my current packaging I have kept the debian specific renaming from > rosegarden -> rosegarden4, however I'm hoping this won Hmm... ? Anyway, there's going to be a 'rosegarden' and probably a compatibility 'rosegarden4' symlink. We can make rosegarden4 or rosegarden a dummy package, and use either one. rosegarden2 can be removed. It is a very different beast, and there might be users, but really, I don't think it's too good an idea to keep something that is only of an archaeological interest. I'm cc'ing the respective bugreports as a final call that rosegarden/rosegarden2 are going to be removed in favor of rosegarden4, and that 'rosegarden' will be a dummy pointing to rosegarden4. regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]