Hi! netpbm has recently switched to a new release system. There does not exist a "latest" and a "stable" version of the package anymore, but it is developed in three series ("advanced", "stable" and "super stable"; see URL). The equivalent to the old "latest" seems to be "advanced", but "advanced" will not be released as a gzipped tarball which can be downloaded from SourceForge.net. Instead the package has to be checked out from SVN[1][2]. As can be seen from SVN, the current "advanced" and "stable" release is 10.35.02. The current "super stable" -- this is the only series which is released as gzipped tarball -- release is at version 10.26.31[3]. It would be nice if portage could contain these newest versions. Also I am interested in how the SVN releases will be handled. Best regards Christian [1] http://svn.sourceforge.net/viewvc/netpbm/ [2] http://sourceforge.net/svn/?group_id=5128 [3] http://sourceforge.net/project/showfiles.php?group_id=5128&package_id=64780
i'm not going to roll svn snaps 10.26.31 is already in portage
Wouldn't it be better then, if 10.26.31 was marked stable and 10.34 unstable? I think so because fixes for 10.34 will be incorporated in >10.35 -- which will not reach portage for several years.
SpanKY, sorry that I have to reopen this bug. Could you please give me some input on comment #2? Personally I have no problem with the fact that you do not want to repackage SVN releases, but I think then you shouldn't leave 1.34 stable. Indeed 1.34 contains a bug which is fixed in 1.35.02 and 1.26.31 which is annoying for me. So I propose that the super stable branch of netpbm should be stable in portage, and all ebuilds of other branches should be removed or masked. Best regards Christian
no, 10.34 contains a lot more features than 10.26.31
