Markus Wichitill wrote:
Stas Bekman wrote:
Markus Wichitill wrote:
Stas Bekman wrote:
Randy Kobes wrote:
For the protocol/echo_nonblock.t test, as I mentioned,
the failure of the last test (which is expected to timeout)
only occurred when running the full test suite. I'll
try to narrow it down - on
Stas Bekman <[EMAIL PROTECTED]> writes:
> So A-T installs into INSTALLSITEARCH because that's where mp2 normally
> installed things to. So why did it now install things outside of arch?
It looks like the top-level httpd-test/perl-framework/Makefile
wasn't picking up your redefinitions; they were
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
so what perl and MM versions are you talking about (now and before)? It has
been installing itself into blib/lib and not (blib/lib/Apache2) for years I
believe. I can't find any notes in Changes saying that it was changed.
OK, I see the
Stas Bekman <[EMAIL PROTECTED]> writes:
> so what perl and MM versions are you talking about (now and before)? It has
> been installing itself into blib/lib and not (blib/lib/Apache2) for years I
> believe. I can't find any notes in Changes saying that it was changed.
OK, I see the problem now.
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
but I'm not sure why do you see what you
explain. mp2/Apache-Test/Makefile should be:
INST_LIB = ../blib/lib
and not:
INST_LIB = ../blib/lib/Apache2
which one do you see?
The first one now, INST_LIB=../blib/lib, which does looks o
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
> but I'm not sure why do you see what you
> explain. mp2/Apache-Test/Makefile should be:
>
> INST_LIB = ../blib/lib
>
> and not:
>
> INST_LIB = ../blib/lib/Apache2
>
> which one do you see?
The first one now, INST_LIB=../blib/lib, which does looks
David Wheeler wrote:
On Nov 22, 2004, at 6:37 AM, Stas Bekman wrote:
Really? I for one believe that the docs would be of better overall
quality if they were maintained at the same time as the rest of the
tree. On smaller-scale CPAN modules, I've found that insisting that
contributors provide patche
Geoffrey Young wrote:
Joe Schaefer wrote:
I recently noticed that mp2 installs its own
Apache::Test under the Apache2 directory. As
a separate CPAN module, Apache::Test gets
installed somewhere else. Since Apache::Test
does not depend on mp2, I think it's a bug for
mod_perl to install it unde
Joe Schaefer wrote:
[...]
IMO the question boils down to your expectations for using
the /branch subdir. Branch management is a PITA in cvs, but
it's transparent in svn. Do you expect development
on modperl-1 codebase to need lots of branch work?
You never know.
If so, I think it makes sense fo
Joe Schaefer wrote:
> I recently noticed that mp2 installs its own
> Apache::Test under the Apache2 directory. As
> a separate CPAN module, Apache::Test gets
> installed somewhere else. Since Apache::Test
> does not depend on mp2, I think it's a bug for
> mod_perl to install it under Apache
I recently noticed that mp2 installs its own
Apache::Test under the Apache2 directory. As
a separate CPAN module, Apache::Test gets
installed somewhere else. Since Apache::Test
does not depend on mp2, I think it's a bug for
mod_perl to install it under Apache2.
Does anybody else agree with
Joe Schaefer <[EMAIL PROTECTED]> writes:
> I like psvn.el for managing svn projects with emacs, and I
> also use compilation buffers to post-process Apache::Test and
> Test::More output (such buffers allow you jump right to the
> source of a failed test, but they work for grep output also).
I jus
On Nov 22, 2004, at 6:37 AM, Stas Bekman wrote:
Really? I for one believe that the docs would be of better overall
quality if they were maintained at the same time as the rest of the
tree. On smaller-scale CPAN modules, I've found that insisting that
contributors provide patches for all three of co
>
> of course, I guess you could argue that to get README-SVN you
> would already need svn access, but you could point users to
> viewcvs or whatever :)
>
Svn is always accessable via normal http/https request and a broswer (at
least for the HEAD revision), so you could pass simply the URL for
>> I think apr is most similar in this respect:
>>
>> apr/apr/
>> apr/apr-util/
>
>>
>
>> so I guess it makes sense to have
>> /perl/modperl
>> /perl/modperl-docs
>>
>> however, both apr and httpd have put solid and currently maintained
>> branches
>> under /branches/, leaving /trunk for
Geoffrey Young wrote:
I suppose that explains very well the reasoning for httpd layout. httpd
folks believe apache-1.3 is a history, and hiding it in a branch makes
it easier to make it so.
I don't think they think that at all :)
There are and there are...
Right. At the moment we have 3 projects i
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
> I suppose that explains very well the reasoning for httpd
> layout. httpd folks believe apache-1.3 is a history, and hiding
> it in a branch makes it easier to make it so.
Err, I don't think they're trying to hide anything. It's
right alongside t
> I suppose that explains very well the reasoning for httpd layout. httpd
> folks believe apache-1.3 is a history, and hiding it in a branch makes
> it easier to make it so.
I don't think they think that at all :)
> Right. At the moment we have 3 projects in perl pmc. And those are
> modperl1, m
Dominique Quatravaux wrote:
Hello, just a grain of salt from an somewhat experienced mod_perl user
who switched to Subversion some time ago...
Stas Bekman wrote:
>
>> Second, docs/ was placed under modperl/ because like most other
>> projects, the convention is to place the website/documentation
Joe Schaefer wrote:
David Wheeler <[EMAIL PROTECTED]> writes:
Actually, I think that if the httpd folks had heard Stas'
argument that modperl1, modperl1 and modperl-docs are three
unrelated projects,
modperl-1 differs from modperl-2 about as much as apache-1.3
differs from httpd-2.0. It looks
Hello, just a grain of salt from an somewhat experienced mod_perl user
who switched to Subversion some time ago...
Stas Bekman wrote:
>
>> Second, docs/ was placed under modperl/ because like most other
>> projects, the convention is to place the website/documentation
>> beside trunk/ of the projec
21 matches
Mail list logo
