Portage 2.1.6.4 em processo de estabilização

Uma nova versão estável do Portage esta chegando, e apesar do changelog não ser muito grande, temos algumas mudanças interessantes desde a série 2.1.4.x:

portage-2.1.6
==================================

* FEATURES=fixpackages is now enabled by default via make.globals. Set
  FEATURES="-fixpackages" in make.conf if you'd like to disable it.
* File collision protection is now enabled by default via make.globals with
  FEATURES=protect-owned. In order to protect files from be overwritten or
  removed a inappropriate times, it is recommended to leave protect-owned
  (or the similar collision-protect feature) enabled at all times.
* The python namespace for portage has been sanitized, all portage related code
  is now contained within the portage namespace. External script should be
  updated accordingly, though links exist for backward compability.
* -* support in package.keywords was changed as it was inconsistent with 
  ACCEPT_KEYWORDS behavior (also see
  http://dev.gentoo.org/~genone/docs/KEYWORDS.stupid).
  Previously having -* in package.keywords matched packages with KEYWORDS="-*",
  now it resets the ACCEPT_KEYWORDS list for the given atom like it does when
  used in ACCEPT_KEYWORDS.
  For packages that don't specify any other KEYWORDS you can use the new **
  token as documented in portage(5) to disable KEYWORDS filtering completely.

portage-2.1.5
==================================

* The pkg_postinst phase is now called after the previous version of a
  package has been removed. As a consequence, it is no longer possible
  to call has_version in pkg_postinst to detect whether the current
  install operation is an upgrade or downgrade. If this information is
  needed during the pkg_postinst phase, do the has_version call in an
  earlier phase (such as pkg_preinst) and store the result in a global
  variable to be accessed by pkg_postinst when it is called. Bug #226505
  tracks all issues related to this phase execution order change.
* The metadata-transfer feature is now disabled by default. This disables the
  "Updating Portage cache" routine that used to run at the tail end of each
  `emerge --sync` operation. If you use something like the sqlite module and
  want to keep all metadata in that format alone (useful for querying), enable
  FEATURES="metadata-transfer" in make.conf. You should also enable
  FEATURES="metadata-transfer" if you have any eclasses from PORTDIR_OVERLAY
  that override eclasses from PORTDIR (in this case, you may have disabled
  a relevant warning message by setting PORTAGE_ECLASS_WARNING_ENABLE="0" in
  make.conf).
* The parallel-fetch feature is now enabled by default. It is optimized
  to avoid doing redundant checksums for previously downloaded files that have
  the correct size. Run `tail -f /var/log/emerge-fetch.log` in a
  terminal to view parallel-fetch progress. Add FEATURES="-parallel-fetch"
  to /etc/make.conf if you want to disable this feature.

Vale notar que este changelog são sobre novas features e mudanças no comportamentos do Portage e não engloba os bugfixes.

Para ver todos os bugs corrigidos desde o 2.1.4.x, basta ver esta entrada no Bugzilla. Como podem ver tivemos 140+ bugs consertados nesta nova versão do Portage.

Segundo zmedico, as únicas diferenças entre esta versão e a 2.2_rcX, é que a série 2.1.6.x não suporta:
1) package sets
2) preserve-libs
3) ACCEPT_LICENSE

Retirando estas 3 novas features, o 2.2_rcX (atualmente em hardmask para estimular o uso e teste da versão 2.1.6.x) é igual a esta nova versão.

Para a estabilização da versão 2.1.6.4, esta sendo necessário que o eselect-news versão 20080320 também fique estável. O eselect-news é uma ferramenta para a leitura de notícias do gentoo, como definido na GLEP 42 (Gentoo Linux Enhancement Proposals).

Até o momento as arquiteturas amd64 e sparc já marcaram os dois ebuilds como estáveis, muito em breve as outras arquiteturas deverão estar marcando também e assim teremos o lançamento oficial do Portage 2.1.6.4.