This only happens with USE="doc". The ebuild fails saying that octave.dvi does not exist. Other than that all software is compiled and ready to install. Therefore, USE="doc" requires a patch to the makefile (or else the ebuild needs to be revised). Here is a patch to the makefile for now: --- octave-2.9.17_orig/doc/interpreter/Makefile.in 2007-10-26 20:22:05.000000000 +0200 +++ octave-2.9.17/doc/interpreter/Makefile.in 2007-11-14 13:27:31.000000000 +0100 @@ -151,7 +151,7 @@ $(SED) -e 's/@@/ at /g' -e 's/@[a-zA-Z]*//g' $< | spell > $@.tmp mv $@.tmp $@ -all: octave.info octave.pdf octave-a4.pdf HTML/index.html +all: octave.info octave.pdf octave.dvi octave-a4.pdf HTML/index.html .PHONY: all $(TEXINFO): src-DOCSTRINGS scripts-DOCSTRINGS munge-texi$(BUILD_EXEEXT) Reproducible: Always
Created attachment 136535 [details, diff] patch to 'octave-2.9.17_orig/doc/interpreter/Makefile.in'
Oh, sorry, this ebuild isn't even in portage yet, it's in my own overlay!!! In any event, I'll attach the ebuild that's in my overlay :) That is the _suggested_ version that people download from the octave website, not the _stable_ version.
Created attachment 136537 [details] octave-2.9.17.ebuild This ebuild is not yet in portage, but it should be marked as ~x86 (at least) since it is the _suggested_ version that should be downloaded from the octave website. I still find that there are some very minor bugs that need to be fixed upstream, but I have not encountered anything major so far that would prevent the average end-user from upgrading.
Submit this upstream please, we cannot fix non-existent ebuilds.
This was originally (accidentally) filed as an application bug, and then I realized that it wasn't even in the main portage tree, but in one of my own ebuilds. The previous comments contain a candidate ebuild & patch for the makefile for =sci-mathematics/octave-2.9.17. Whoever had replied to me before told me to push it upstream, so I thought I'd just submit the ebuild, since it wasn't already in the portage tree. ... this is the 'suggested' version of the software that the octave website urges people to download.
ps: I thought it wouldn't be necessary to open a new bug just to submit my ebuild, that's why I re-opened it. I followed the instructions below for submitting: http://www.gentoo.org/doc/en/ebuild-submit.xml
Oh, OK. Thanks :)
Hi Christopher, Thanks much for your ebuild. Presently, the octave ebuild development is taking place in the science overlay (it has octave-2.9.17) which also contains ebuilds for all the new-style split octave-forge ebuilds (see bugs #153462 and #179885, there you can also find more information regarding the development process). Hence, if this is alright I close this bug as fixed and please let us know about any enhancements/problems with the current octave/octave-forge versions in the overlay at the above mentioned bugs. Thanks much, Markus
Oh, ok ;-) I just read some of the other bugs - good idea to split up the forge sections like that ;-) I'll close this one, thank you for the info though ;-)
