Inkscape has daily SVN activity, but is almost always buildable and usable at a given revision. The attached ebuild is derived from: http://gentoo-overlays.zugaina.org/alloverlays/roslin/media-gfx/inkscape/inkscape-9999.ebuild Where the proper ESVN handling was particularly helpful. Then the diff to the current inkscape ebuilds was minimized. The result is attached to this bug. Some additional work remains for this to conform to Gentoo coding standards. In particular the 'sh autogen.sh' and './configure' lines have autotools equivalents, I think. Reproducible: Always
Created attachment 207767 [details] inkscape-9999.ebuild live SVN ebuild Needs autotools, configure and a few other cleanups.
Sorry, no live ebuilds to Portage ...
OK, happy to defer to Gentoo developer judgment on that, but it's not exactly the case that no live ebuilds are in portage at this time: # find /usr/portage -name "*9999*" |wc -l 361 Are you referring to some initiative to move live ebuilds to overlays? That would be a reasonable thing.
(In reply to comment #3) > OK, happy to defer to Gentoo developer judgment on that, but it's not exactly > the case that no live ebuilds are in portage at this time: Sure if you want you can start your own overlay for inkscape and maintain it. Similar way inkscape's live ebuild would needed a dedicated maintainer, where as now it's maintained by group of people looking and several hundred ebuilds at once. It would go too quickly in a poor shape and fixing it would take too much time. Only trying to be realistic here ;) This can change when inkscape gets a own maintainer at any time.
Created attachment 348934 [details] Updated, Bazaar based ebuild This is my (probably terrible) update to the ebuild. Uses bzr instead of svn. Compiled for me, today. I'm not proposing to change RESOLVED WONTFIX, just putting this here for people to find.
