[ previous ] [ next ] [ threads ]
 
 From:  Manuel Kasper <mk at neon1 dot net>
 To:  Stefan Frank <Mono dot General at RootServices dot Biz>
 Cc:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Looking for some version explanations ( OS/Patches/GUI )
 Date:  Sat, 18 Mar 2006 19:14:59 +0100
[taking this to m0n0wall-dev since it really doesn't belong on the
general mailing list]

On 15.03.06 01:57 +0100, Stefan Frank wrote:

> The Developers Handbook mostly points to files/scripts
> at http://m0n0.ch/wall/downloads which should be used
> to create a own environment to create images from scratch.
> 
> Is this Link only as archive or will it be updated from time
> to time? I know that there is a SVN Repository available.

It will be updated as necessary. The current version of the
developers' handbook explains how to use SVN to get the latest
version of phpconf and the webGUI. The idea is to fetch other files
needed for building images (kernel configs, patches etc.) from the
repository as well. As you've discovered, the "build" folder in trunk
already contains most of what's needed, so the developer's handbook
could be changed if somebody gets the chance.

> Can the webGUI from the latest trunk be used on 4.11?

Yes.

> Will it be considered that the latest/trunk webGUI works
> with FreeBSD 4.11 without trouble?

Yes, as long as we don't actually move to something else.

> Whats about the idea to add checks in the webGUI that
> prove the running OS and disable/hide features that are
> not possible (for example if its not supported by the
> old Kernel?) That will be fine for me imho ;)

I'd prefer not to start mixing up operating system and webGUI/phpconf
versions. There are too many dependencies and it's just not worth the
effort. When/if we move to FreeBSD 6.0, trunk will be copied to a new
maintenance branch, then all the files in trunk will be modified as
necessary.

> In the SVN Repository is a "build" folder in /trunk/ but
> in /tags/release-1.21/ is no "build" folder. Has this any
> reason? How should users be able to check for changes
> in the older/stable versions of monowall?

Tags are *never* changed. Changes may only be committed to branches
or the trunk. The build folder was introduced after 1.21 was tagged.
The next tagged version (probably 1.22) will have one as well.

> If possible then it will be nice if somebody add the files
> related to monowall 1.2.x brunch in /tags/release-1.21/

No, if anybody commits to a tag directory they'll have their SVN
commit access revoked. ;)

- Manuel