On 8/20/07, Alessandro Tanasi <email address hidden> wrote:
> I consider to deploy a separate package with web interface, in my packages.
So, if we can't modify the package, does that mean that you want the
same package in repositories twice, one with the web interface
dependencies, and on without? I think the web interface is a huge
part of msf3, especially for people who will be using it on Ubuntu.
If we left that out, it would be a major detriment. Otherwise, we
would need th same package in the repos twice (metasploit3 and
metasploit3-web)...
> Are you a kind of pedantic guy? svn stay for nickname of subversion ;)
I just wanted to make sure the package name was termed correctly. If
you make the package RECOMMEND 'svn' apt will not resolve this
package, as it is not valid. svn is the command name and not the
package name. Yes, pedantics are my specialty :-p
--
Kristian Erik Hermansen
On 8/20/07, Alessandro Tanasi <email address hidden> wrote:
> I consider to deploy a separate package with web interface, in my packages.
So, if we can't modify the package, does that mean that you want the
same package in repositories twice, one with the web interface
dependencies, and on without? I think the web interface is a huge
part of msf3, especially for people who will be using it on Ubuntu.
If we left that out, it would be a major detriment. Otherwise, we
would need th same package in the repos twice (metasploit3 and
metasploit3-web)...
> Are you a kind of pedantic guy? svn stay for nickname of subversion ;)
I just wanted to make sure the package name was termed correctly. If
you make the package RECOMMEND 'svn' apt will not resolve this
package, as it is not valid. svn is the command name and not the
package name. Yes, pedantics are my specialty :-p
--
Kristian Erik Hermansen