Opened 19 years ago
Closed 18 years ago
#7349 closed enhancement (fixed)
NEW: p5-apache-test 1.27
Reported by: | narf_tm@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.2 |
Keywords: | Cc: | narf_tm@… | |
Port: |
Description
Apache-Test 1.27
the portfile can be found here: ATTACHED
Description: Test.pm wrapper with helpers for testing Apache
Homepage: http://search.cpan.org/~pgollucci/Apache-Test-1.27/lib/Apache/Test.pm
Attachments (2)
Change History (10)
Changed 19 years ago by narf_tm@…
Attachment: | p5-apache-test-1.27.tar.gz added |
---|
comment:1 Changed 19 years ago by blb@…
Owner: | changed from darwinports-bugs@… to blb@… |
---|---|
Status: | new → assigned |
comment:3 Changed 19 years ago by narf_tm@…
I just installed mod_perl2 and it seems to include Apache::Test. This means if you try to install mod_perl2 with this port you get a conflict.
comment:4 Changed 19 years ago by blb@…
Owner: | changed from blb@… to darwinports-bugs@… |
---|---|
Status: | assigned → new |
(In reply to comment #4)
I just installed mod_perl2 and it seems to include Apache::Test. This means if you try to install mod_perl2 with this port you get a conflict.
Hmm, looks like; however, the files don't conflict, but this is due to the fact that mod_perl2 doesn't install its perl modules into the vendor_perl structure, as DP perl modules should. This may be a bug with mod_perl2. But how to deal with this particular issue is a good question. In theory, mod_perl2 should probably disable its own installing of it then require this...
comment:5 Changed 18 years ago by markd@…
Type: | defect → enhancement |
---|
comment:6 Changed 18 years ago by markd@…
Cc: | narf_tm@… added |
---|
Looks like the mod_perl conflict has been dealt with upstream. From the Apache::test 1.28 ChangeLog:
remove the mod_perl.pm entry from %INC after Apache::Test finishes initializing itself. because both mp1 and mp2 share the entry, leaving it around means that Apache::Test might prevent later modules from loading the real mod_perl module they're interested in, leading to bad things [Geoffrey Young]
comment:7 Changed 18 years ago by narf_tm@…
The problem is this port conflicts with mod_perl2. The mod_perl2 port includes the Apache::Test module. So you get the following error if you try to install this after mod_perl2:
---> Activating p5-apache-test 1.28_0+apache2 Error: Target com.apple.activate returned: Image error: /opt/local/share/man/man3/Apache::Test.3.gz is being used by the active mod_perl2 port. Please deactivate this port first, or use the -f flag to force the activation. Error: Status 1 encountered during processing.
I am not sure about how to deal with this. How many people use the Apache::Test module outside of mod_perl? Could we just put in a warning that says that this port is not needed with the mod_perl2 port? Could we change the mod_perl2 to not include the Apache::Test module and add it as a port dependacy instead? Any ideas of how to make this work?
comment:8 Changed 18 years ago by markd@…
Resolution: | → fixed |
---|---|
Status: | new → closed |
Version 1.28 fixed the mod_perl conflict. It has been committed.
Port