Today I’d like to bring you some information on the pending irssi-cvs to irssi-svn move. Upstream Irssi developers changed from CVS to Subversion as their version control system already a couple of months ago and we’re now following this change with our live ebuilds.
Now to the point that makes this a little bit tricky. irssi-cvs is currently marked stable on hppa, ppc, sparc and x86. This is just inappropriate for a live ebuild, because we (as in Gentoo developers) have no way to verify the state of the source code. Moreover we can’t verify the integrity of downloaded files, that means we expose our users to some security risk.
To cut a long story short, we’re going to keyword irssi-svn ~arch only and I’m going to push this move out as an automatic move via our regular updates files. The new irssi-svn ebuild has a version number higher than the old irssi-cvs ebuild. For our ~arch users this means that they will see this as an update to irssi-svn after the move is done on their local system. For arch users with current portage versions the move will be done and they will see no update and no error message, if no package depends on irssi-svn. They will stay at the same version of irssi they had before. If they want to emerge irssi-svn, they will get the familar ‘All ebuilds that could satisfy “irssi-svn” have been masked.’ message. Stable users are free to take a look at “Mixing Software Branches” from our handbook, on how to use irssi-svn on their stable system.