g-octave news: the octave overlay

After having lots of problems with people that can't use g-octave properly, sometimes because they don't seems to be able to read documentation, elog messages and/or just ask, and after a suggestion of Sebastien Fabbro (bicatali), I write down some simple scripts to update the g-octave package database and an overlay using g-octave and a cronjob.

I built a virtual machine on my own server and set up a weekly cronjob, that will hopefully keep the packages up-to-date.

The overlay is available on Github:


To install it, follow the instrunctions available on the README file. The overlay is available on layman, named octave.

Packages with unresolvable dependencies, e.g. packages with dependencies unavailable on gentoo-x86, aren't available in the overlay. If you find some package that is supposed to work and isn't available on the overlay please open an issue on Github, and I'll take a look ASAP.

As a bonus, g-octave code itself was moved to Github:


Feel free to submit pull requests if you think that something is broken and you know how to fix it.

And as another bonus, the g-octave website (http://g-octave.org/) is now running on the Read the Docs service, that is way more reliable than my own server. This should avoid the recent documentation downtimes.

Project homepages for slackers

Warning: This project is deprecated. Look at http://rafaelmartins.eng.br/projects/

Create a homepage and documentation for a project is a boring task. I have a few projects that were not released yet due to lack of time and motivation to create a simple webpage and write down some Sphinx-based documentation.

To fix this issue I did a quick hack based on my favorite pieces of software: Flask, docutils and Mercurial. It is a single file web application that creates homepages automatically for my projects, using data gathered from my Mercurial repositories. It uses the tags, the README file, and a few variables declared on the repository's .hgrc file to build an interesting homepage for each project. I just need to improve my READMEs! :)

It works similarly to the PyPI Package Index, but accepts any project hosted on a Mercurial repository, including my non-Python and Gentoo-only projects.

My instance of the application lives here (not anymore):


The application is highly tied to my workflow, e.g. the way I handle tags and the directory structure of my repositories on my server, but the code is available in a Mercurial repository:


Most of my projects aren't listed yet, and I'll start enabling them as soon as I fix their READMEs.


This is just a quick (and late) post about FISL 13, that happened at Porto Alegre/RS, Brazil, from July 25th to 28th.

It was a really cool conference, and I had the first chance to meet another Collaboran (Thiago Santos), and lots of people that I just knew from the Internet.

I had an activity in the schedule. It was a talk/BoF about Google Summer of Code, with some discussions and lightning talks about the projects developed by the present students and mentors. I presented an introduction about the Google Summer of Code and moderated the discussions and lightning talks. Pretty cool! :)

Thanks to my employer Collabora for sponsoring the trip.

Deploying blohg to bitbucket

Bitbucket is a repository hosting service widely used by Mercurial users. Its basic plan is free and includes unlimited private repositories.

Some people don't know, because it isn't widely advertised, but Bitbucket provides free web hosting for static files. Any files stored in a repo called username.bitbucket.org will be served from http://username.bitbucket.org/. It just works for user names, as far as I know.

Read more