As illustrated in the link, I received confirmation that the svn repo is dead and should no longer be used. Gimp uses now git, so if anything the ebuild should be converted to git. Either that, or simply erased from the tree. Reproducible: Always Actual Results: The ebuild uses subversion. Expected Results: The ebuild should use git. The svn repo is still up but no development take place there any longer.
Created attachment 206186 [details, diff] Convert ebuild from subversion to git This patch sets up the ebuild so it uses the new git repository instead of the abandoned subversion one. There's where all the development is taking place right now. The patch is trivial and so far, it seems to work without a problem here.
Created attachment 209340 [details] A very poor ebuild to build gimp from git. Very simple / poor ebuild to simply pull the current gnome. Simply runs automake.sh --disable-gtk-doc and make / make install 's.
well, could this patch then be included in the three? It is not convenient, to apply it every time a portage sync was done before one wants to emerge gimp-9999
(In reply to comment #3) > well, could this patch then be included in the three? > > It is not convenient, to apply it every time a portage sync was done before > one wants to emerge gimp-9999 > That's why you should put the patched ebuild in an overlay. However, I agree that this needs to be fixed, the ebuild on its current status is just useless.
as of now ebuild from portage uses git repo. bug can be closed probably
(In reply to comment #5) > as of now ebuild from portage uses git repo. bug can be closed probably > and open another one, because the one who put it live didn't tested it with -doc use flag :-\
I've already filed the corresponding bug #296242
Gimp live ebuild was migrated to git. so this bug is fixed.
