Joe Schaefer wrote:
> Geoffrey Young <[EMAIL PROTECTED]> writes:
>
> [...]
>
>
>>I really don't see how it can be any other way - I absolutely,
>>positively do not want to deal with questions about how prior beta
>>versions mix with later beta versions and, eventually, the official
>>2.0.
>
>
Geoffrey Young <[EMAIL PROTECTED]> writes:
[...]
> I really don't see how it can be any other way - I absolutely,
> positively do not want to deal with questions about how prior beta
> versions mix with later beta versions and, eventually, the official
> 2.0.
So then, the proposed branch is a re
On Sun, 20 Mar 2005, Geoffrey Young wrote:
> To take a look at the codebase you can checkout the following branch
> from subversion:
>
> http://svn.apache.org/repos/asf/perl/modperl/branches/apache2-rename-unstable
>
> and test and install it as usual.
For those Win32 users wishing to give this a
>
> make dist has a problem, so I can't roll a tarball at the moment.
try this
http://cvs.apache.org/~geoff/mod_perl-unstable.tar.gz
--Geoff
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAI
Geoffrey Young <[EMAIL PROTECTED]> writes:
> I would expect that, barring any new developments,
> we should be able to roll a candidate by monday
> at the latest.
-1, let's not rush things. We're not all on the same
page right now, even as developers, so there needs
to be some/lots of formal v
Adam Kennedy wrote:
>> Anybody know if this branch actually solves our current CPAN issues
>> with trunk? It'd royally suck if we just displaced the known
>> CPAN/installer problems with trunk with a whole new set of
>> CPAN/installer problems associated with this branch.
>
>
> I have to say I
> "Geoffrey" == Geoffrey Young <[EMAIL PROTECTED]> writes:
Geoffrey> - first, assume lazy consensus if nobody hollers with something new
that
Geoffrey> we haven't already heard and discussed ad nauseum
Mark me as a lazy consenter. :-)
--
Randal L. Schwartz - Stonehenge Consulting Service
Adam Kennedy wrote:
>> no, the mp2 MakeMaker tools serve many purposes, and installing into
>> Apache2
>> is just one of them. another is, for instance, letting XS modules know
>> where the mod_perl header files and typemaps are, or (IIRC) adding things
>> that, say, win32 needs to know about.
>
no, the mp2 MakeMaker tools serve many purposes, and installing into Apache2
is just one of them. another is, for instance, letting XS modules know
where the mod_perl header files and typemaps are, or (IIRC) adding things
that, say, win32 needs to know about.
so no, they stay. but now pure perl m
Adam Kennedy wrote:
>> yes, it would suck, but I don't see how it would cause new problems.
>> Apache2:: is a namespace like any other, and it previously did not
>> exist, so
>> I would expect it to install like any other namespace but not stomp on
>> prior
>> existing stuff, which were the big c
yes, it would suck, but I don't see how it would cause new problems.
Apache2:: is a namespace like any other, and it previously did not exist, so
I would expect it to install like any other namespace but not stomp on prior
existing stuff, which were the big concerns.
Indeed. And the other half of t
Joe Schaefer wrote:
> Geoffrey Young <[EMAIL PROTECTED]> writes:
>
> [...]
>
>
>> - you cannot make, test, or install the unstable branch over any
>>other version of mod_perl-1.99
>
>
> Blech. IMO that's a rather serious problem with this branch.
> Any thoughts on how it could be fixed
Anybody know if this branch actually solves our current CPAN
issues with trunk? It'd royally suck if we just displaced
the known CPAN/installer problems with trunk with a whole new
set of CPAN/installer problems associated with this branch.
I have to say I'm yet to take a detailed look at this
Joe Schaefer wrote:
> Geoffrey Young <[EMAIL PROTECTED]> writes:
>
> [...]
>
>
>> - mod_perl.pm is now mod_perl2.pm
>>
>> - Apache2.pm no longer exists
>
>
> Procedural question: how should we vote on
> this stuff? At this point, I think we should
> treat this proposal as just that, a p
Geoffrey Young <[EMAIL PROTECTED]> writes:
[...]
>
> - mod_perl.pm is now mod_perl2.pm
>
> - Apache2.pm no longer exists
Procedural question: how should we vote on
this stuff? At this point, I think we should
treat this proposal as just that, a proposal.
Any ideas about how, and when, we
Geoffrey Young <[EMAIL PROTECTED]> writes:
[...]
> - you cannot make, test, or install the unstable branch over any
> other version of mod_perl-1.99
Blech. IMO that's a rather serious problem with this branch.
Any thoughts on how it could be fixed?
[...]
> If you have issues or concerns
Tom Schindl <[EMAIL PROTECTED]> writes:
> What's going to happen to Apache::Request will it also follow this
> direction and renamed Apache2::Request?
TBD- I think that issue depends on what folks say about the
current renaming proposal for mp2. In the past the apreq-dev
has always honored the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
my svn-client refuses to checkout from the repository telling me that
the URL-Schema is unknown. Are there any tar.gz's to download or even
better does anybody know what that means(does my distribution forgot to
add this protocol). I'm using Mandrak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What's going to happen to Apache::Request will it also follow this
direction and renamed Apache2::Request?
Tom
Joe Schaefer wrote:
| Geoffrey Young <[EMAIL PROTECTED]> writes:
|
| [...]
|
|
|>The process has reached the point where discussion ought to m
Geoffrey Young <[EMAIL PROTECTED]> writes:
[...]
> The process has reached the point where discussion ought to move back
> into the general community - the majority in the PMC have a proposed
Apologies- late correction: it's more accurate to say "a co
Stas Bekman wrote:
gSOAP acct wrote:
Hi Stas,
I think I got the cvs version of modperl you mentioned
...
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic
co modperl-2.0
... Is that right?
Right.
> modperl_constants.c:1576: error: `AP_MPMQ_RUNNING'
> undeclared (first use in this function)
I
Stas Bekman wrote:
gSOAP acct wrote:
Hi Stas,
I think I got the cvs version of modperl you mentioned
...
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic
co modperl-2.0
... Is that right?
Right.
> modperl_constants.c:1576: error: `AP_MPMQ_RUNNING'
> undeclared (first use in this function)
I
gSOAP acct wrote:
Hi Stas,
I just decided to upgade things ...
[...]
... everthing seem to compile and install correctly.
Good for you :) Bad for others, as now we don't know what was the problem and
the we will have to go through the same thing again with the next person
encountering that exact
ignore my last email. Geez I am stupid sometimes.
--- gSOAP acct <[EMAIL PROTECTED]> wrote:
> Hi Stas,
>
> I just decided to upgade things ...
>
> so I did this ...
>
> cvs -d
> :pserver:[EMAIL PROTECTED]:/home/cvspublic
> login
> cvs -d
> :pserver:[EMAIL PROTECTED]:/home/cvspublic
> co modper
Hi Stas,
I just decided to upgade things ...
so I did this ...
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic
login
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic
co modperl-2.0
#To get the cutting edge Apache 2.0 and APR 0.9
projects:
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic
co -
gSOAP acct wrote:
Hi Stas,
Well that got me a lot closer but make test still
failed. Should I upgrade my Apache and try again with
modperl 2.0?
Not really. It should work fine with 2.0.48.
t/apache/subprocess.t 255 65280?? ?? %
??
t/apr/perlio.t 255 65280?? ?? %
Hi Stas,
Well that got me a lot closer but make test still
failed. Should I upgrade my Apache and try again with
modperl 2.0?
$ make test
...
t/preconnection/noteok
t/protocol/echo.ok
gSOAP acct wrote:
Hi Stas,
I think I got the cvs version of modperl you mentioned
...
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic
co modperl-2.0
... Is that right?
Right.
> modperl_constants.c:1576: error: `AP_MPMQ_RUNNING'
> undeclared (first use in this function)
I know what the problem i
Hi Stas,
I think I got the cvs version of modperl you mentioned
...
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic
co modperl-2.0
... Is that right?
Next I do this ...
perl Makefile.PL MP_APXS=/usr/local/apache2/bin/apxs
... and now when I do my make I get this ...
cc -I/home/Plankton/cvs
[remember to reply back to the list! Thanks]
gSOAP acct wrote:
I forgot about having mod_perl and perl built with the
same compiler. I'll rebuild perl and if that doesn't
work I'll get the current modperl cvs and try again as
you suggest.
I think you *need* to use modperl cvs. If I were you I'd d
gSOAP acct wrote:
-8<-- Start Bug Report
8<--
1. Problem Description:
I get a lot of test failures when I run make test.
but you showed us the failure of the first one. I guess a lot more fail, right?
Please get the current modperl cvs and try again. Most l
On Fri, 4 Jan 2002, Stas Bekman wrote:
> > but yes, registry scripts would need some sort of protection as well.
>
> I cannot see where registry scripts differ from handlers, from the
> access to internals point of view. Once you run under mod_perl it
> doesn't matter what you do. You've to ha
On Sun, 6 Jan 2002, Sebastian Bergmann wrote:
> Randy Kobes wrote:
> > Great ... If you're trying next 'nmake test', you may find
>
> Haven't tried 'nmake test' yet, but: Apache.exe crashes on shutdown
> when mod_perl is loaded.
Yes, that happened before with an earlier modperl-1.3?; it was
On Sun, 6 Jan 2002, Sebastian Bergmann wrote:
> I can't build a debug version of mod_perl by setting MP_DEBUG=1 when I
> run Makefile.pl, the compiler barks out with unknown compiler flags. So,
> no stacktrace.
i have perl on win32 built with debugging, so modperl inherits the debug
flags
Randy Kobes wrote:
> Great ... If you're trying next 'nmake test', you may find
Haven't tried 'nmake test' yet, but: Apache.exe crashes on shutdown
when mod_perl is loaded.
Reminds me: What changes do I have to make to httpd.conf, besides the
obvious
LoadModule perl_module modules/l
On Sat, 5 Jan 2002, Sebastian Bergmann wrote:
> Thanks for your help, it builds fine now.
Great ... If you're trying next 'nmake test', you may find
some problems with not being able to find certain modules
in @INC. This is because, due to case-insensitive filenames
on Win32, perl copying a 'L
Randy Kobes wrote:
> Ah ... That's probably the problem - modperl is looking for
> certain header files in the MP_AP_PREFIX parent directory,
> and if they're not found, the error you got would result.
Thanks for your help, it builds fine now.
--
Sebastian Bergmann
http://sebastian-bergma
On Sat, 5 Jan 2002, Sebastian Bergmann wrote:
> Randy Kobes wrote:
> > No, it shouldn't be - the install to \server\apache should also
> > copy the needed include and lib files. And there's no spaces in
> > the names, so it's not croaking on that ... If it doesn't make
> > any difference to you,
On Sat, 5 Jan 2002, Stas Bekman wrote:
> I thought his question was abouthow to make INC private
> to various vh's. The answer is that it's done.
>
> Have I misinterpreter the question? Or are we talking
> about different things?
ah, i must have misread the last message.
of course, there is sti
Jay Lawrence wrote:
> Stas,
>
> Thank you for the link. I was not aware of this document. The PerlOptions
> directive looks like an excellent design decision!
Thank Doug for designing/implementing, not me for sending a link :)
--
_
y Young" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, January 04, 2002 9:25 PM
Subject: Re: mod_perl 2.0 for ISPs
> Jay Lawrence wrote:
>
> > Another point that was mentioned by someone in my local Mongers group
> > was that of different INC paths for differ
brian moseley wrote:
> On Sat, 5 Jan 2002, Stas Bekman wrote:
>
>
>>Guys, I suggest that you read the design docs before you
>>continue. The INC issue has been addressed already.
>>Please read:
>>http://apache.org/~dougm/modperl_2.0.html
>>http://apache.org/~dougm/modperl_design.html
>>
>
> th
Sebastian Bergmann wrote:
> C:\home\apache\modperl-2.0>perl makefile.pl MP_USE_DSO=1
> MP_GENERATE_XS=1 MP_AP_PREFIX=c:\server\apache
Just noticed that MP_AP_PREFIX should point to the binary directly on
*NIX, so I tried
perl makefile.pl MP_USE_DSO=1 MP_GENERATE_XS=1
MP_AP_PREFIX=c:
Randy Kobes wrote:
> No, it shouldn't be - the install to \server\apache should also
> copy the needed include and lib files. And there's no spaces in
> the names, so it's not croaking on that ... If it doesn't make
> any difference to you, what happens if you install to C:\Apache2?
> That works f
On Sat, 5 Jan 2002, Stas Bekman wrote:
> Guys, I suggest that you read the design docs before you
> continue. The INC issue has been addressed already.
> Please read:
> http://apache.org/~dougm/modperl_2.0.html
> http://apache.org/~dougm/modperl_design.html
that may not be exactly what he's wish
Jay Lawrence wrote:
> Another point that was mentioned by someone in my local Mongers group
> was that of different INC paths for different sets of users. I confess not
> to
> have given this much thought but upon initial thinking it seems that if
> different users want to have isolated local mod
On Fri, 4 Jan 2002, Sebastian Bergmann wrote:
> Randy Kobes wrote:
> > Is this a binary install of Apache2, or one that you compiled
> > yourself from the httpd-2.0 cvs sources?
>
> I always build from the sources myself. The sources, however are
> located in c:\home\apache\httpd-2.0, not in
Another point that was mentioned by someone in my local Mongers group
was that of different INC paths for different sets of users. I confess not
to
have given this much thought but upon initial thinking it seems that if
different users want to have isolated local modules (differing versions
of the
Randy Kobes wrote:
> Is this a binary install of Apache2, or one that you compiled
> yourself from the httpd-2.0 cvs sources?
I always build from the sources myself. The sources, however are
located in c:\home\apache\httpd-2.0, not in c:\server\apache\. Is this
a problem?
--
Sebastian B
On Fri, 4 Jan 2002, Sebastian Bergmann wrote:
> Randy Kobes wrote:
> > Is C:\server\apache the directory to which Apache2 was installed?
>
> Yes, and C:\Server\Apache\bin\Apache.exe is the executable.
Is this a binary install of Apache2, or one that you compiled
yourself from the httpd-2.0 cvs
Randy Kobes wrote:
> Is C:\server\apache the directory to which Apache2 was installed?
Yes, and C:\Server\Apache\bin\Apache.exe is the executable.
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Did I help you? Consider a gift: http://wishl
On Fri, 4 Jan 2002, Sebastian Bergmann wrote:
> What am I doing wrong, now?
>
> C:\home\apache\modperl-2.0>perl makefile.pl MP_USE_DSO=1 MP_GENERATE_XS=1
> MP_AP_PREFIX=c:\server\apache
> Reading Makefile.PL args from @ARGV
>MP_USE_DSO = 1
>MP_GENERATE_XS = 1
>MP_AP_PREFIX = c:\serv
Stas Bekman wrote:
>
> >>I think the first thing to lookat is how PHP builds the jail.
> >>
> >
> > two different issues, no? one is about normal cgi/registry scripts
> > and the other about accessing areas of the server through the API.
> >
> > but yes, registry scripts would need some sort of
>>I think the first thing to lookat is how PHP builds the jail.
>>
>
> two different issues, no? one is about normal cgi/registry scripts
> and the other about accessing areas of the server through the API.
>
> but yes, registry scripts would need some sort of protection as well.
I cannot see
Stas Bekman wrote:
>
> Geoffrey Young wrote:
>
> > hi all...
> >
> > I was wondering if any thought was given to designing mod_perl 2.0
> > with ISPs in mind. I know this issue has cropped up on modperl@ but
> > I've been thinking about it lots lately and have an idea (well, some
> > rambling
Geoffrey Young wrote:
> hi all...
>
> I was wondering if any thought was given to designing mod_perl 2.0
> with ISPs in mind. I know this issue has cropped up on modperl@ but
> I've been thinking about it lots lately and have an idea (well, some
> ramblings, anyway)...
agreed that there is
Yeah I also think that 'cause we lack such a support beat mod-Perl so
much !! In the time it is much more powerfull than PHP or so, lacking
support for mass-hosting doesn't give a chance for mod_perl to make it
most widly used..
my 5c
[EMAIL PROTECTED]
-
On Sat, 29 Sep 2001, Ask Bjoern Hansen wrote:
>
> running
>
> /home/smtpd/apps/apache/bin/httpd -X -d /home/smtpd/src/modperl-2.0/t -f
>/home/smtpd/src/modperl-2.0/conf -DAPACHE2 -DPERL_USEITHREADS
>
> gives me a line like this in the error_log:
>
> /usr/libexec/ld-elf.so.1:
>/home/smtpd/ap
On Tue, 19 Jun 2001, Jeffrey A. Stuart wrote:
> Umm.. 5.7.1 is a devel release... yes? (Sorry, I meant stable... I assumed
> that 5.7 would at some point be the stable branch or is perl taking the linux
> kernel route?)
yeah, from perldelta.pod:
=head2 Improved Perl version numbering system
, June 19, 2001 4:38 PM
To: Jeffrey A. Stuart
Cc: modperl-2.0 dev-list
Subject: RE: mod_perl 2.0
On Tue, 19 Jun 2001, Jeffrey A. Stuart wrote:
> Ok.. :) Next question... Will mod_perl work with perl 5.005 or 5.6? (IE is
> perl 5.7 due out soon?)
% head -1 modperl-2.0/Makefile.PL
use 5.006;
On Tue, 19 Jun 2001, Jeffrey A. Stuart wrote:
> Ok.. :) Next question... Will mod_perl work with perl 5.005 or 5.6? (IE is
> perl 5.7 due out soon?)
% head -1 modperl-2.0/Makefile.PL
use 5.006;
5.7.1 has already been released, 5.7.2 is due soonish. it is possible
modperl-2.0 will require 5.8
Subject: RE: mod_perl 2.0
On Tue, 19 Jun 2001, Jeffrey A. Stuart wrote:
> Ok, is mod_perl 2.0 alpha, beta, stable, what? :)
unreleased, pre-alpha, stable-ish. apache-2.0 is still a moving target,
as is bleedperl (5.7.2-dev), so its easy for a change in either of those
to break the modperl-
On Tue, 19 Jun 2001, Jeffrey A. Stuart wrote:
> Ok, is mod_perl 2.0 alpha, beta, stable, what? :)
unreleased, pre-alpha, stable-ish. apache-2.0 is still a moving target,
as is bleedperl (5.7.2-dev), so its easy for a change in either of those
to break the modperl-2.0 cvs.
> it will be worth the wait if you're currently using 1.xx on win32 :)
I've tried out 1.something and definately want mod_perl(!) but 1.x on
win32 is not an option since Apache (on win32) runs threaded using only 1
process (actually 2) and one instance of mod_perl only handle 1 request at
a time.
Ok, is mod_perl 2.0 alpha, beta, stable, what? :)
--
Jeff Stuart
[EMAIL PROTECTED]
-Original Message-
From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 18, 2001 11:16 PM
To: Jeffrey A. Stuart
Cc: modperl-2.0 dev-list
Subject: Re: mod_perl 2.0
modperl-2.0 in cvs works
modperl-2.0 in cvs works with apache-2.0, see 1.x's mod_perl_cvs.pod,
replace 'modperl' with 'modperl-2.0' to check it out.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Mon, 18 Jun 2001, Kurt George Gjerde wrote:
> Hi,
>
> Has anyone tried building 2.0 for win32 yet, or is this too early?
too early.
> I tried this a couple of weeks ago without any luck.
>
> (I'm eagerly waiting for multi-threading support :)
it will be worth the wait if you're currently
On Fri, 25 May 2001, Gerald Richter wrote:
> At the moment there are differences, but they aren't so great, but Greg is
> about to change the some of the interfaces in 2.0.
>
> My first step would be to implement a version of 1.x (but keep 2.0) in mind
> (Because I need it now in a production e
Hi Doug,
>
> if you implement an interface to mod_dav that works with both 1.x and 2.x,
> that would be great and then we can skip the inclusion of an interface
> bundled with modperl-2.0. or we could have two, your 1.x version on cpan,
> and a 2.x version bundled with modperl-2.0. i'm not sur
On Thu, 24 May 2001, Gerald Richter wrote:
> Hi Doug,
>
> do you have any plans for supporting mod_dav (which is now part of Apache
> 2.0) in mod_perl 2.0 ?
yes, i would like to have an auto-generated interface for 2.0, but have
not looked at mod_dav yet.
> The reason for my question is, that
On Wed, 28 Mar 2001, Doug MacEachern wrote:
> i like the idea, the pdf output i've seen from your modules is really
> slick! before moving forward, i think we should consider creating a
> modperl-2.0-docs repository, similar to what httpd does, splitting up its
> docs and code. the mod_perl-2.0
>> i like the idea, the pdf output i've seen from your modules is really
>> slick! before moving forward, i think we should consider creating a
>> modperl-2.0-docs repository, similar to what httpd does,
>> splitting up its
>> docs and code. the mod_perl-2.0 dist can include the docs
>> (or subs
> -Original Message-
> From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 28, 2001 9:32 PM
> To: Stas Bekman
> Cc: modperl-2.0 dev-list
> Subject: Re: mod_perl 2.0 documentation converters
>
>
> i like the idea, the pdf output i&#
i like the idea, the pdf output i've seen from your modules is really
slick! before moving forward, i think we should consider creating a
modperl-2.0-docs repository, similar to what httpd does, splitting up its
docs and code. the mod_perl-2.0 dist can include the docs (or subset of),
but a sepe
On Thu, 13 Jul 2000, Doug MacEachern wrote:
> On Mon, 10 Jul 2000, Randy Kobes wrote:
>
> >For one thing, there's various conflicts with
> > some apache and perl symbols, like stat, etc.
> > on Win32, just as with mod_perl-1.2x - these
[ ... ]
>
> argh. are those symbol conflicts something
75 matches
Mail list logo
