I think, it should be stored in dev-embeded/uisp/uisp-9999.ebuild
Created attachment 87855 [details] The new ebuild
Created attachment 87856 [details] Changelog of the new ebuild
What is the purpose of having a live CVS ebuild for this in the tree? Or, put in other words, what functionality found in CVS HEAD and not in a release warrants the extra work of maintaining a live CVS ebuild for this?
(In reply to comment #3) > [...] what functionality found in CVS HEAD and not in a release > warrants the extra work of maintaining a live CVS ebuild for this? I'd say none, as their cvs hasn't been updated since their last release for which we already have an ebuild in Portage (uisp-20050207-r1.ebuild). Denis.
(In reply to comment #3) > What is the purpose of having a live CVS ebuild for this in the tree? Or, put > in other words, what functionality found in CVS HEAD and not in a release > warrants the extra work of maintaining a live CVS ebuild for this? Strangely, after a "emerge --search uisp", I didn't find it. So, instead of search more deeply, I wrote it. So this is absolutely not useful for now, and I plea people to excuse me for the noise.