I hacked together ebuilds for all the dependencies that are newer than the latest Gentoo ebuilds, but I built Lily by hand, since FontForge generates the sandbox violations. Apparently FontForge wants to periodically write its status to ~/.PfaEdit which of course violates the sandbox.
However, I was just now looking at the official Gentoo ebuild for 2.5.2, and in the "src_compile" function, there is a series of 4 "addwrite" statements. So, as root, you ought to mkdir ~/.PfaEdit (if you don't already have such a directory) and then, in your modded ebuild, add an "addwrite ~/.PfaEdit" just underneath the other addwrites. Addwrite basically pokes a specific hole in the sandbox without causing a violation. I haven't tried this yet; let me know if you get it to work.
If that doesn't work, here's how to build by hand:
#!/bin/bash
#set up build dir, download source mkdir /var/tmp/lilypond-build cd /var/tmp/lilypond-build wget http://www.lilypond.org/ftp/v2.5/lilypond-2.5.8.tar.gz tar xzf lilypond-2.5.8.tar.gz cd lilypond-2.5.8
#configure and make export lilypond_datadir="/usr/share/lilypond" export local_lilypond_datadir="/usr/share/lilypond/2.5.8" ./configure make || exit 1 # use next line only if you want to install documentation make web || exit 1 make install || exit 1 # use next line only if you want to install documentation make out=www web-install || exit 1
#put docs and resources in Gentoo-friendly places
mkdir -p /usr/share/lilypond/2.5.8/buildscripts/out
cp buildscripts/out/lilypond-profile /usr/share/lilypond/2.5.8/buildscripts/out/
cp buildscripts/out/lilypond-login /usr/share/lilypond/2.5.8/buildscripts/out/
cp buildscripts/out/lilypond-clean-fonts /usr/share/lilypond/2.5.8/buildscripts/out/
cp buildscripts/out/lilypond-words /usr/share/lilypond/2.5.8/buildscripts/out/
mkdir -p /usr/share/lilypond/2.5.8/elisp/out
cp elisp/*.el /usr/share/lilypond/2.5.8/elisp/
cp elisp/out/lilypond-words.el /usr/share/lilypond/2.5.8/elisp/out/
mkdir -p /usr/share/lilypond/2.5.8/vim/out
cp vim/out/lilypond-words.vim /usr/share/lilypond/2.5.8/vim/out/
cp vim/lilypond*.vim /usr/share/lilypond/2.5.8/vim/
cp vim/vimrc /usr/share/lilypond/2.5.8/vim/
mkdir -p /usr/share/doc/lilypond/html
# use next line only if you want to install documentation
mv /usr/local/share/doc/lilypond/2.5.8 /usr/share/doc/lilypond
cp AUTHORS.txt /usr/share/doc/lilypond/
cp COPYING /usr/share/doc/lilypond/
cp ChangeLog /usr/share/doc/lilypond/
cp DEDICATION /usr/share/doc/lilypond/
cp INSTALL.txt /usr/share/doc/lilypond/
cp NEWS.txt /usr/share/doc/lilypond/
cp README.txt /usr/share/doc/lilypond/
cp ROADMAP /usr/share/doc/lilypond/
cp THANKS /usr/share/doc/lilypond/
cp VERSION /usr/share/doc/lilypond/
#Finally, perform post-install housecleaning . /usr/share/lilypond/2.5.8/buildscripts/out/clean-fonts
MichaÅ DwuÅnik wrote:
On Fri, 14 Jan 2005 09:29:31 -0800, Daniel Johnson
<[EMAIL PROTECTED]> wrote:
After a great deal of struggle, I finally got 2.5.7 to compile and
install yesterday on my Gentoo box, but I've had a few font issues.
Have you prepared a set of ebuilds needed ? I would be grateful for posting them. I still have sandbox errors building 2.5.7 using my puny tries to produce an ebuild :)
Regards
MichaÅ
_______________________________________________ lilypond-user mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-user
