I like to submit a new package to the Sunrise Overlays Project for httest, the HTTP test tool (http://htt.sourceforge.net). I've made all the required files and will attach them to this ebuild. Imho the category shoud be net-analyzer.
According to http://overlays.gentoo.org/proj/sunrise/wiki/HowToCommit I have to open a bug report for submitting the ebuild and assign it to maintainer-wanted@… or maintainer-needed@... I don't know how to do that (there's no form element on the submit bug page for that), can someone reassign the ticket if it is not assignet correctly.. thanks
Created attachment 300027 [details]
Created attachment 300029 [details]
Created attachment 300031 [details]
Created attachment 300033 [details]
I tested the httest tool on x86 and amd64, both archs work well with the exception of the htntlm tool not yet working correctly on amd64, therefore the unstable keyword.
Please follow Portage naming scheme when uploading ebuilds to
Bugzilla, e.g. httest-2.1.16.ebuild
Your src_compile and src_install are basically default implementations
so there's no need to specify them in ebuild. You may consult
http://devmanual.gentoo.org/ to see if you really need to write your
own ebuild phase functions.
What does the extraconf variable do?
Do not set keywords to stable when submitting new ebuild even if
you've tested it yourself on your machine
Apart from this ebuild worked fine for me, although some tests failed
(In reply to comment #6)
> Your src_compile and src_install are basically default implementations
> so there's no need to specify them in ebuild.
Turns out the you actually need src_install since it was no-op until EAPI-4.
InOverlay keyword is wrong for this package - it can not be found in layman overlays, so i have dropped it
(In reply to comment #8)
> InOverlay keyword is wrong for this package - it can not be found in layman
> overlays, so i have dropped it
Is it not in sunrise?
(In reply to comment #9)
> Is it not in sunrise?
No, it is not, at least for now