Gentoo Archives: gentoo-science

From: Rafael Goncalves Martins <rafael@×××××××××××××××××.br>
To: gentoo-science@l.g.o
Subject: [gentoo-science] [GSoC] g-Octave - roadmap to 0.3
Date: Fri, 02 Jul 2010 19:31:40
Message-Id: 20100702192752.GA27478@nyquist
Hi guys,

g-Octave 0.2 was released, as early announced here by me, then is time to
start the work on the next version (0.3), although the tinderbox tests for the
new package database are still pending. The patches for individual packages can
be done in parallel with the g-Octave main development.

The next version will come with 3 main new features:

Support to optional logging

I'm planning to use the 'logging' module, from the Python standard library in
order to implement this. The implementation will allow the user to enable or
disable the logging feature from the configuration file.

Support to package updates

g-Octave can't do package updates by now. All that the user can do is
reinstall the package manually when he knows that the package is updated by
the upstream.

The idea is to implement an g-octave CLI option that query the package manager
about upgrades in the installed packages and do the update for the user.

Support to Paludis/Pkgcore

g-Octave currently can only use emerge/portage to do the installation of
packages. Although g-Octave should keep using the portage API internally, the
users will be able choose one of the package manager frontends as they want.

When I say "portage API" I mean the support to colors on the CLI and the
stuff to do version comparations and create manifest files, basically. All
the great stuff, like overlay management, package masking and the package
installation itself will be done by the user's package manager of choice.

Some ideas and thoughts about that?


Rafael Goncalves Martins