first of all let me thank you for the release of 3.0 although I think that you screwed up some things like too many rcX, preX, etc. and the fact that releasing a new ntop version is now something very formal that is not part of my behaviour. The release cycle changed in the last 1.5 years: we don't release often and wait too long. This is the last time we make this mistake: every 6 months we should schedule a major release. That should be our goal.
Second: some decision need to be taken together. Why did you start with .50 and not with .1? Somehow I feel you're taking over the project. as you ask what to move where you should do the same. I'm pretty sure you don't want to do that but looking at some of these actions I feel that somehow there's some truth behind this.
Finally. Every month I receive private complains from people who say that you're unpolite in some of your reply. As you know I hardly have time for reading all the emails so I should be the last person who could speak about this subject. However even in this respect I believe that there's some truth behind this. Please, since 3.0.x be nice(er) and understand that not all of you know as much as you know.
Again: you've done a great job so far. Please take these notes as positive suggestions not as critics. We need to improve and I would like to do this together with you and the rest of the ntop community.
Your question: go ahead with what you suggested (OSX files belong to the <os> branch).
Cheers, Luca
Burton M. Strauss III wrote:
Luca:
As we start 3.0.50, some suggestions to re-arrange the ntop cvs tree, which are to move packages into a separate module (like ntcsh). This will keep content out of the .tgz and binary packages and make life easier. Problem now is that the files are always one release out dated unless you go through wild gyrations.
Suggested structure:
packages/ common/ ntop.init ntop.conf.sample <os>/
i.e.
./FreeBSD-ports ... ./MacOSX ./linux ./linux/debian ./linux/Fedora ./linux/Gentoo ./linux/Mandrake ./linux/RedHat ./linux/SuSE ./OpenBSD-ports ./Win32
Do the installer/MacOSX/xxxx files belong in here too?
(Setting up the module and directories is something you need to do, otherwise it usually locks up the cvs)
-----Burton
-- Luca Deri <[EMAIL PROTECTED]> http://luca.ntop.org/ Hacker: someone who loves to program and enjoys being clever about it - Richard Stallman
_______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
