apachetoolbox-devel Mailing List for ApacheToolbox (Page 4)
Brought to you by:
bryanandrews
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(15) |
Jul
(4) |
Aug
(1) |
Sep
(7) |
Oct
(3) |
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(29) |
Aug
|
Sep
(7) |
Oct
(4) |
Nov
(2) |
Dec
(5) |
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
From: Bryan <io...@da...> - 2001-06-26 17:30:37
|
Testing pending messages. -Bryan |
From: Bryan <io...@da...> - 2001-06-26 17:29:20
|
Alias test. -Bryan |
From: Kevin J. M. Jr. <km...@WP...> - 2001-06-22 16:08:39
|
Hey, Got another idea. Apache 2.0.x support. I mentioned this once for the 1.5.x release, but ATB 2.0 would probably coincide more with this. Also, I figured this would be helpful to the Apache Group, as more people could try it out and report bugs and what not. -- Kevin |
From: Kevin J. M. Jr. <km...@WP...> - 2001-06-20 16:14:40
|
Hey, I was just thinking . . . 2.x should have better binary support. I think it'd be damn cool to be able to build .deb files for each module + apache, or them all combine, etc. etc. Hell, we could even make ATB a deb itself, and then use apt-get to get new versions. Of course, this would extend to RPMs and FreeBSD if feasible. -- Kevin |
From: Kevin J. M. Jr. <km...@WP...> - 2001-06-18 19:56:51
|
If this message goes through without moderation needed, then the de...@ap... alias is gonna be a pain, because it needs to be moderated. If this gets stopped, then the entire list is moderated, which is a major PITA for devel list :-P -- Kevin |
From: Kevin J. M. Jr. <km...@WP...> - 2001-06-18 19:53:58
|
Are we gonna slap every beta release up on www.apachetoolbox.com? Or just functional ones? ;) (I wouldn't think we'd need a FreshMeat listing though). -- Kevin |
From: Bryan <io...@da...> - 2001-06-18 18:49:00
|
de...@ap... forwards to this mailing list now. -Bryan |
From: Bryan <io...@da...> - 2001-06-18 18:47:27
|
---------- Forwarded message ---------- Date: Mon, 18 Jun 2001 15:45:56 +0200 From: Dominique Lechaudel <lec...@in...> To: br...@ap... Subject: ApacheToolBox on HP-UX Hello Bryan, I am french so sorry for my poor english. First : apachetoolbox is a great tools ! I use it for compiling apache/php on HPUX A few step are required to run it on HP-UX : - get BASH - remove grep -w from the script (load-settings : please see attachement) a warning is already present (i don't know where : "./install.sh: return: too many arguments") All is working fine for the rest ! On my host : $ echo `uname` HP-UX Thanks for your work. Gratefully, -- *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ Dominique LECHAUDEL E-Mail : lec...@in... D=E9partement des Syst=E8mes d'Information Tel : 03 83 50 46 00 poste 8630 C.N.R.S. - I.N.I.S.T. 2, all=E9e du parc de brabois 54514 VANDOEUVRE Cedex FRANCE Serveur institutionnel : http://www.inist.fr Serveur applicatif : http://services.inist.fr *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ |
From: Bryan <io...@da...> - 2001-06-18 18:25:16
|
Testing. Thanks for all the fish! On Mon, 18 Jun 2001, Kevin J. Menard, Jr. wrote: > Hey Bryan, > > > Monday, June 18, 2001, 1:01:27 PM, you wrote: > > BA> apa...@so... I > BA> believe. "6-12 hours" before it's live, I really > BA> doubt it'll take that long. You can I are the > BA> only ones on it at the moment, it's a public list. > > > Up already. > > |
From: Kevin J. M. Jr. <km...@WP...> - 2001-06-18 17:36:00
|
Heya fellas, Guess I'll write the first email to the list. And really, there's only two people on it, including myself, so perhaps "fellas" isn't appropriate, but I'm writing it for the archives ;) Bryan set up the mailing list so we can lay out some design goals. This email list is not for general troubleshooting questions or how to use ATB or any of its component software. It's for the further development of ATB. If you have trouble with a function you're writing, ask it here. If you have a question about whether or not a module should be included, ask it here. Basically, if it pertains to the development of ATB, ask it here, otherwise, go to the forums at www.apachetoolbox.com I guess to start, discussion on certain design goals, methods, and other implementation details should be ensued. With the 2.0 release, ATB is moving from shell scripting to perl. Perl is cross-platform, extensible, and damn cool. It should relieve all the problems that have existed with Solaris and *BSD users in particular. The original thinking was that everyone has a shell, not everyone has perl, and that really was good thinking. But shells are not the same from platform to platform, for some God-forsaken reason. So, the new rationale is, if you don't have perl, you shouldn't be running a server anyway ;) Seriously, nearly every *NIX system comes stock with a perl distro now, and it'd be easier for a user who doesn't, to just get perl, rather than ATB try to tailor to that. So. To begin with, I'd like to throw some ideas out there. Should ATB stay procedural, as it pretty much is now, or take an OO approach. Ideally, I would think each module could be represented as an object of a module class (and in the case of php, sub modules). It may be harder to implement, and Perl OOP gets messy, but the idea is that any new module can be defined by just creating a new object. Certain properties exist in all modules (URL to get it from, gunzip/untar'ing it, and so forth). Bryan also suggested removing the cache file in preference of an array structure (dump the output?). Perl's text capabilities are awesome, so this should not be a problem :) I was even thinking maybe a gtk interface at some point, since Perl places nicely with that. But that's really something at the very bottom of my list, since I don't run X on any of my servers ;) Well, hopefully this list will help out with the progression of the 2.0 release of ATB. Probably be best if most, if not all, interaction between developers goes through the lists for the sake of archiving. Likewise, please search the archives before asking questions. Blah blah. And any new ideas? Let's get the planning phase going! -- Kevin |