On 02/28/2010 03:28 PM, D. Michael McIntyre wrote: > On Sunday 28 February 2010, Dave Plater wrote: > > >> When I package rosegarden for openSUSE I place examples and templates under >> /usr/share/rosegarden >> > >> Patch attached. >> > So when you package Rosegarden, you hack it up and make arbitrary changes, > then you want to upstream a patch that refers to your local changes, even > though in the hands of everyone else in the world, it will break exactly the > problem you aimed to solve with the patch. > > We can't accept this. > > In theory, we could accept this accompanied by another patch to actually > install the files to the location you want to load them from, but that would > break our intent to put these files in userland where they are readily > modified, and we have no desire to do that. It is frequently necessary to > make minor changes to these files one time on any individual user's system to > get them to play, and the intent behind all of this was to make it possible > to > save them in place. > > If you want to break that, it's your baby. > I didn't expect you to accept the patch. An rpm cannot place files in the users home directory that can only be done by rosegarden. After installing rosegarden from an rpm, not sure about apt, the user is presented with buttons in the file open dialog that don't point to any examples or templates. To fix this problem I made the patch, if your intention is for the example and template files and in fact any other files, to go in the users home directory it has to be done on first use by rosegarden. The patch is a workaround for this problem and this message is to bring the problem to your attention and maybe any other packager that hasn't noticed the problem. The files have to be copied from ./data/ after make install as part of the rpm %install stage. Sorry if the way I worded the message caused offense. Regards Dave P
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
