| 1 |
> Do you know how much "members" the "gentoo octave" project have? |
| 2 |
My guess is that theres is only one or none. |
| 3 |
|
| 4 |
> Each sentence you write make this more obvious. |
| 5 |
Whatever you say. |
| 6 |
|
| 7 |
> 1) You DON'T need to use Github to update the package database. |
| 8 |
> There's a big and shiny warning on this section of the docs saying |
| 9 |
> that end-users don't need to read. Just do it if you want to help |
| 10 |
> other users. Use the --scm option of g-octave, and package.keywords to |
| 11 |
> unmask the scm packages you want to install. |
| 12 |
> 2) You DON'T need to use --sync at all, g-octave can install packages |
| 13 |
> from octave-forge SVN repository with the damn --scm option. |
| 14 |
I don't want to install the svn packages from octave-forge repository. I want to install the lastest stable packages from octave-forge. Which is something I cannot do unless I follow some instructions in the docs that, as an end user, I'm not supposed to read. |
| 15 |
|
| 16 |
> 3) stable releases of g-octave comes with a package database, that is |
| 17 |
> installed by 'emerge --config'. We do this for security reasons. The |
| 18 |
> live version obviously don't comes with a package database, then you |
| 19 |
> need the '--sync' option to get one from github. |
| 20 |
So I can't use the lastest stable versions of octave-packages unless I use the unstable and masked software and somebody manually mantains an external database. I can't see how this is easier for the end user. |
| 21 |
|
| 22 |
Thanks for your time, but I think is easier, faster and better for me if I mantain my own ebuild-based repo. |
| 23 |
|
| 24 |
Cheers, |
Archives