From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OUlxZ-00075c-Oq for garchives@archives.gentoo.org; Fri, 02 Jul 2010 19:31:40 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E2533E08A1; Fri, 2 Jul 2010 19:31:11 +0000 (UTC) Received: from mail-gx0-f181.google.com (mail-gx0-f181.google.com [209.85.161.181]) by pigeon.gentoo.org (Postfix) with ESMTP id C551FE08A1 for ; Fri, 2 Jul 2010 19:31:11 +0000 (UTC) Received: by gxk2 with SMTP id 2so820412gxk.40 for ; Fri, 02 Jul 2010 12:31:11 -0700 (PDT) Received: by 10.101.106.7 with SMTP id i7mr1391934anm.176.1278099071286; Fri, 02 Jul 2010 12:31:11 -0700 (PDT) Received: from nyquist ([189.83.23.132]) by mx.google.com with ESMTPS id m11sm2380307ybn.4.2010.07.02.12.31.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 02 Jul 2010 12:31:10 -0700 (PDT) Date: Fri, 2 Jul 2010 16:27:52 -0300 From: Rafael Goncalves Martins To: gentoo-science@lists.gentoo.org Subject: [gentoo-science] [GSoC] g-Octave - roadmap to 0.3 Message-ID: <20100702192752.GA27478@nyquist> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-science@lists.gentoo.org Reply-to: gentoo-science@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Archives-Salt: 68605fdf-8d7c-4855-b3d3-9b4def1c53b9 X-Archives-Hash: 6618afffda5f4ef4a7e5e634c17dba9b --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 mana= ger 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, t= he 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? Thanks! --=20 Rafael Goncalves Martins http://rafaelmartins.eng.br/ --0F1p//8PRICkK4MW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iQEcBAEBAgAGBQJMLj24AAoJEMmH5mwCk1NvXygIAIWuPmIOSv4tY65nSK6F2NUd 1ptS3g9W+KonRXx4heeNdfvI0FEYun6kqjsH7jGhjED14BmVjwzoRjktFU60TH6b OdHy9sIIV14K9QTsmwi08fMDvQe9nokJu/jn0WHbBd53TGIirt1l2UQdHwOjqlBk 8GhsAUrboGY+kRsfJz1kie/kYiff8S8wkUShK0YyNg/0c+MheLjubLQELXUVoh/v 4pJ91K9EzEVs4sigLdHtRSHLY/bN9lPDQTCzTHUDeiV4aEylfkjQYS0MAlLIxU0X Asa5qRvoNzqiSGUY3reVH7GxgENBefpqHyN7xn5yFWHRVlinCbzdPZGN2o/LUMs= =SaSB -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW--