[openbeos] Re: Apache 2.0
- From: Nik Derewianka <nick@xxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Wed, 26 Jun 2002 11:00:30 +1000
Bruno G. Albuquerque wrote:
So, what you're saying is that the 2 guys running BeBits have to
download every app ever posted and check if they work? I guess you
won't get that. :)
heheh no not at all. What i am saying is that just like there is a bad
link report button, it would be handy to have a 'broken application'
button. Ie newer users are going to get rather frustrated when they
download an app and it doesnt work (nor could it ever work).
As to the rest of the responses, it might help if i try clarifying
things a wee bit:
Currently im taking on a small simplish project to refamiliarise myself
with the BeApi's etc. So i was thinking that i would do something that
gets rid of the unacceptable (for end users) practice of
download/configure/make/make install - i chose apache as it is a very
useful program, has had a major beos porting effort and there will be
many non-CLI people using it. So basically i allow the snapshot zip to
be dropped on my app, it autounzips, then offers a compile options
interface for which modules can be compiled into apache and then the
next interface is for configuring the httpd.conf file - the aim is to
get the benefits of compile from source, with the simplicity of at least
IIS, but i hope to make it simpler/friendlier than that. Thus i dont
want a precompiled binary, as my app will be the one to create it.
If there is a list thats more appropriate for this kind of stuff -
please point me to it.
Regards,
Nick
- References:
- [openbeos] Re: Apache 2.0
- From: Bruno G. Albuquerque
Other related posts:
- » [openbeos] Apache 2.0
- » [openbeos] Re: Apache 2.0
- » [openbeos] Re: Apache 2.0
- » [openbeos] Re: Apache 2.0
- » [openbeos] Re: Apache 2.0
- » [openbeos] Re: Apache 2.0
- » [openbeos] Re: Apache 2.0
- » [openbeos] Re: Apache 2.0
- [openbeos] Re: Apache 2.0
- From: Bruno G. Albuquerque