On Monday 18 Apr 2011 12:16:26 D. Michael McIntyre wrote:
> On Monday, April 18, 2011, Nick Bailey wrote:
> > This patch to makefile.in is all that's needed to get the tunings.xml
> > file
> 
> > installed in the right place. I made rosegarden by saying:
> I wish I'd thought to look at this while I still had a bit of time.  You
> don't want to install this, you want to bundle it and unpack it to
> userland with the rest of the data files.
> 
> I'd be happy to knock that out for you right quick, if only it weren't
> bedtime.
> 
> It's a simple enough undertaking I might be able to get it done before next
> weekend, if I don't forget.  I'll probably forget though.
That's extraordinarily kind of you.

If your package system runs make install with a different prefix, or inside a 
chroot, at least make install should put tuings.xml in the right place with 
this patch applied. However, my understanding (and I've been looking at the 
autoconf docs as a refresher) is that makefile.in is produced by automake on 
reading makefile.am. But there is no makefile.am in the co'd main branch, so I 
don't really know which file to patch. Patching makefile.in is surely a recipe 
to have the change overwritten the next time automake gets invoked.

Nick/.


------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

Reply via email to