Kristian Hermansen, thanks again for marking the other bug as a duplicate. I missed this one when I added.
I too have a packaged version, from the unmodified metasploit release, it is more then possible to build the deb with the SVN, as SVN is used to update the exploits, and other framework modules. May not be the ideal build, but can work.
Either way, if you want to modify the "original package" we can simply write a patch, and place it in the debian/ directory. But again, doesn't seem modifications are necessary, everything builds fine. And that is when we start to interfere with the license.
The real issue here isn't the "ease" of packaging metasploit, but the license itself.
So do we have the license issue resolved? In what other ways can I assist? Alessandro Tanasi we should trade .changes to see where we can improve the package, before upload to REVU.
I am really looking forward to getting metasploit in the Ubuntu repositories.
Kristian Hermansen, thanks again for marking the other bug as a duplicate. I missed this one when I added.
I too have a packaged version, from the unmodified metasploit release, it is more then possible to build the deb with the SVN, as SVN is used to update the exploits, and other framework modules. May not be the ideal build, but can work.
Either way, if you want to modify the "original package" we can simply write a patch, and place it in the debian/ directory. But again, doesn't seem modifications are necessary, everything builds fine. And that is when we start to interfere with the license.
The real issue here isn't the "ease" of packaging metasploit, but the license itself.
So do we have the license issue resolved? In what other ways can I assist? Alessandro Tanasi we should trade .changes to see where we can improve the package, before upload to REVU.
I am really looking forward to getting metasploit in the Ubuntu repositories.
Thanks,
Justin M. Wray