[Wifidog] What's up next?

[Philippe April]

Oh and btw...

The compiling procedure for libhttpd seems broken. Another reason why we
should think about just compiling it with WiFiDog...

Whether you specify prefix or not, it will install into /usr/local/lib and
/usr/local/include

:)

That, plus the fact that we actually install a customized patch, I say we
put the patched sources into WiFiDog (as a separate dir if you want) and
build directly with it.

The author of libhttpd has used his makegen and autoconf files from
another product he makes (mini-sql) and still has values about msql into
his makefiles.

So either we include the sources with WiFiDog, or we fix his broken build
and install scripts.

Philippe

> Also "make dist" does not seem to work. It seems it's because of the
> dist_sysconf_DATA variable in Makefile.am (it's also giving a warning when
> I autogen.sh).
>
> I took it out and it seems to work fine now. Benoit can you confirm it's
> not needed and we can commit into CVS without it?
>
> And if we don't want to bundle libhttpd with WiFiDog, then we should give
> the users the possibility to specify a path to it instead in configure.in.
>
>> 1. We need to figure out what we do with libhttpd. This has been giving
>> me
>> headaches recently. Personally I would either include it with wifidog
>> and
>> make it build at the   same time, or simply include the sources with
>> wifidog, already patched, and just compile with it. That would save a
>> lot
>> of trouble to anyone who'd like to compile it (including --> me..
>> compiling for the wrt54g is a little pain).
>>
>> 2. We need to test multiple connections, the timing out, the classes, at
>> the same time and see if the software stays up forever without crashing
>> and fix any bugs we see.
>>
>> 3. Doxygen documentation :)
>>
>> 4. Add the possibility to have users with no restrictions, in the config
>> file. This will probably require us to return the username to the
>> gateway
>> from the central server with the user profile.
>>
>> Example:
>> User: papril777 at yahoo.com
>> Profile: 5
>> blahblahblah
>>
>> Do a compare with a list of users that have no restrictions in the
>> config
>> file.
>>
>> Not sure if it should be done this way and if it's related to groups at
>> all.
>>
>> Also,
>>
>> We should setup a box somewhere on the net to act as the "central
>> server"
>> for now (or even forever). That way we have a real setup happening.
>>
>> I will have some time to test tonight and saturday.
>>
>> Please add anything else to that list :)
>>
>> Philippe
>>
>>> Okay,
>>>
>>> 	It looks like we've reached stable status on the OpenWRT (more
>>> testing by Phil and maybe Pascal would be great.)
>>>
>>> 	Now, what features are next on the block? I know there's a lot to
>>> do, but I want a good idea of what's most important to work on next.
>>>
>>> Alex
>>>
>>> _______________________________________________
>>> Wifidog mailing list
>>> Wifidog at isf.waglo.com
>>> http://isf.waglo.com/mailman/listinfo/wifidog_isf.waglo.com
>>>
>>
>>
>> _______________________________________________
>> Wifidog mailing list
>> Wifidog at isf.waglo.com
>> http://isf.waglo.com/mailman/listinfo/wifidog_isf.waglo.com
>>
>>
>
>
> _______________________________________________
> Wifidog mailing list
> Wifidog at isf.waglo.com
> http://isf.waglo.com/mailman/listinfo/wifidog_isf.waglo.com
>
>


_______________________________________________
Wifidog mailing list
Wifidog at isf.waglo.com
http://isf.waglo.com/mailman/listinfo/wifidog_isf.waglo.com