On Sun, Sep 18, 2011 at 10:31 AM, Juan Aguado <[email protected]> wrote: >> I wrote a blog post about this topic, to avoid being repetitive. >> >> http://rafaelmartins.eng.br/post/g-octave-past-present-and-future/ >> >> TL;DR: Please read the documentation. >> >> > > First of all, sorry if I've offended somebody. That wasn't my intention. My > intention was only to show the current state of octave in gentoo.
Do you know how much "members" the "gentoo octave" project have? > However, I also find annoying that people assumes that I haven't read the > documentation or made an effort to fix the problems. Each sentence you write make this more obvious. > Anyway, I find more time-consuming to log in in a github account to propose > some changes and wait them to be approved than to update an ebuild of fill a > bug. Not to mention thta when I try to update de g-octave database, I get > this message: '"--sync" not available, please install g-octave-9999 if you > want this.', and I'm forced to install a masked version of a package that, as > the docs says, is not recommended to use. Not to mention that I also have > real life problems and I don't have time to mess with this things. 1) You DON'T need to use Github to update the package database. There's a big and shiny warning on this section of the docs saying that end-users don't need to read. Just do it if you want to help other users. Use the --scm option of g-octave, and package.keywords to unmask the scm packages you want to install. 2) You DON'T need to use --sync at all, g-octave can install packages from octave-forge SVN repository with the damn --scm option. 3) stable releases of g-octave comes with a package database, that is installed by 'emerge --config'. We do this for security reasons. The live version obviously don't comes with a package database, then you need the '--sync' option to get one from github. That's it Regards, -- Rafael Goncalves Martins Gentoo Linux developer http://rafaelmartins.eng.br/
