| 1 |
Hi folks, |
| 2 |
|
| 3 |
I have just released g-octave 0.4, that is probably the last version |
| 4 |
released as part of the SoC. Here are the news of this version: |
| 5 |
|
| 6 |
= Py3k support = |
| 7 |
g-octave modules and the main script were ported to Py3k and will work |
| 8 |
with Python >= 2.6 out of the box. The ebuild will install g-octave |
| 9 |
for all the Python versions available in your system. |
| 10 |
|
| 11 |
= Restrict the use of g-octave to the users/groups allowed to build packages = |
| 12 |
Now only the users that belongs to the user group of the package |
| 13 |
manager (e.g. portage, paludisbuild) are allowed to run g-octave. |
| 14 |
|
| 15 |
= Search of Packages = |
| 16 |
A command-line option (-s/--search) was added to the main script. This |
| 17 |
option will receive an argument, that is the search term or a regular |
| 18 |
expression, and will output a list of matches. |
| 19 |
|
| 20 |
= Package database moved to Git = |
| 21 |
The g-octave package database now lives on a Git repository at GitHub |
| 22 |
[1] and is managed using a new script, that do almost all the work |
| 23 |
automatically. The g-octave main script doesn't depends on Git though, |
| 24 |
it uses the snapshot tarballs generated by Github to install the |
| 25 |
package database to the user. |
| 26 |
|
| 27 |
= New management of live ebuilds = |
| 28 |
The old versions of g-octave did the masking of live ebuilds |
| 29 |
implicitly. The user just needed to type 'g-octave packagename-9999' |
| 30 |
to install the live version of 'packagename'.. This was changed and |
| 31 |
now the user will need to change the value of the variable "use_scm" |
| 32 |
to "true" in the configuration file "/etc/g-octave.cfg". But this will |
| 33 |
not yet install the live version by default, it will create an ebuild |
| 34 |
without keywords. The user will still need to unmask the live version |
| 35 |
in the package manager configuration files. I also added 2 |
| 36 |
command-line options (--scm and --no-scm) that are useful to change |
| 37 |
the behavior of g-octave on the command line interface, without touch |
| 38 |
the configuration file. |
| 39 |
|
| 40 |
= CLI option '--list' rewritten = |
| 41 |
The command-line option '--list' now groups the package versions and |
| 42 |
show the data in a better shape for the user. I also added a |
| 43 |
--list-raw option, that print all the packages available in the |
| 44 |
database to the stdout, one package per line and exit, useful for scripts. |
| 45 |
|
| 46 |
= Added the option '--oneshot' = |
| 47 |
I added the command-line option '--oneshot' to g-octave, that have the |
| 48 |
same behavior in emerge. I just forgot to add it previously. :) |
| 49 |
|
| 50 |
= New script for automated tests = |
| 51 |
I installed a XML-RPC plugin at my trac instance [2] and rewrote my |
| 52 |
script to do automated tests, to use XML-RPC instead of parse the page |
| 53 |
HTML when reporting build errors. |
| 54 |
|
| 55 |
= Proper management of licenses = |
| 56 |
The LICENSE variable of the ebuilds is now filled correctly, based on |
| 57 |
the licenses from ${PORTDIR}/licenses |
| 58 |
|
| 59 |
= Added metadata.xml = |
| 60 |
g-octave now writes a metadata.xml file on the directory with the |
| 61 |
ebuilds, if none. |
| 62 |
|
| 63 |
= New trac instance and domain = |
| 64 |
my g-octave stuff just got new home (thanks ferringb) and a cool |
| 65 |
domain name ( http://g-octave.org ). |
| 66 |
|
| 67 |
That's it! |
| 68 |
|
| 69 |
The ebuild is available on the science overlay and the updated |
| 70 |
documentation is available here: |
| 71 |
http://doc.g-octave.org/0.4/ |
| 72 |
|
| 73 |
[1] - http://github.com/rafaelmartins/g-octave-db |
| 74 |
[2] - http://www.g-octave.org/trac |
| 75 |
|
| 76 |
Sorry for the big read ;-) |
| 77 |
|
| 78 |
Best Regards. |
| 79 |
|
| 80 |
-- |
| 81 |
Rafael Goncalves Martins |
| 82 |
http://rafaelmartins.eng.br/ |
Archives