Summary: | pentest-tools collection ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | sittinglittleduck <james> |
Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | drear |
Priority: | High | Keywords: | EBUILD |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
tar of the ebuild
plain text ebuild New version of the ebuild |
Description
sittinglittleduck
2006-03-10 09:38:18 UTC
Created attachment 81850 [details]
tar of the ebuild
This is the tar of the ebuild I have produced so far
Please attach the ebuild as plain text and reopen. Created attachment 81900 [details]
plain text ebuild
as requested a plain text version of the ebuild
reopened I have added a home page for this ebuild that shows a better breakdown of the tools within the list, as it would appear you cant add comments with the ebuild dependencies list http://www.sittinglittleduck.com/pentest-tools/ Created attachment 97828 [details]
New version of the ebuild
Added a new verison which corrects packages that have changed their name (eg wireshark) and have removed ssldump as it wont compile
Out of curiosity: is this really needed, can a list like this be maintained across several arches, doesn't this depend on personal preferences as well as on what is being tested and can't this be done in a shell script? Is there still any interest in including this in Portage? Personally I echo the sentiment of Jukka, this feels too much like something most people would end up not using and keeping this list up to date would require a lot of effort. This would be more suited for a wiki page now days. Makes sense. Looks like it's closing time, then. |