#42410 closed defect (invalid)
php5: php-config.1.gz already exists and does not belong to a registered port
Reported by: | veltenheyn@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Low | Milestone: | |
Component: | ports | Version: | 2.2.1 |
Keywords: | Cc: | ||
Port: | php5 |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
I get following if i install php55 and then try to install php5 (to get pecl running as it is somehow not included in php55).
Error: org.macports.activate for port php5 returned: Image error: /opt/local/share/man/man1/php-config.1.gz already exists and does not belong to a registered port. Unable to activate port php5. Use 'port -f activate php5' to force the activation.
When I do a 'sudo port contents php55 the file '/opt/local/share/man/man1/php-config.1.gz' is listed. So it should be registered, or not? Should I use 'port -f activate php5' or fix the problem another way?
Change History (5)
comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Component: | base → ports |
---|---|
Description: | modified (diff) |
Keywords: | php55 php5 removed |
Owner: | changed from macports-tickets@… to ryandesign@… |
Port: | php5 added |
Priority: | Not set → Low |
Summary: | php5 conflicts with php55 → php5: php-config.1.gz already exists and does not belong to a registered port |
comment:2 follow-up: 3 Changed 11 years ago by veltenheyn@…
Hy ryan thx for your support,
php55 doesn't provide pecl or pear (there is a php55-pear package but it only contains a ini file). I wan't to use the taint php extension (https://github.com/laruence/php-taint -> pecl install taint). Does macport really want a port for every php extension? If so I'm looking into adding a port request.
I have a relatively fresh macport I moved the php-config.1.gz man files and got php5 to activate.
comment:3 follow-up: 4 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Replying to veltenheyn@…:
php55 doesn't provide pecl or pear (there is a php55-pear package but it only contains a ini file).
php5 doesn't provide pecl or pear either, does it? We removed them years ago because we didn't want users using them, because using them would cause them to install files into the MacPorts prefix, which only MacPorts is supposed to be installing files into.
I wan't to use the taint php extension (https://github.com/laruence/php-taint -> pecl install taint).
I've added it for you in r116995. It doesn't compile with php55 so I only provided php53 and php54 versions of it. PHP extensions are easy to add ports for, so let me know if there are any others you need. Feel free to file tickets, or just email me if that's easier.
Does macport really want a port for every php extension? If so I'm looking into adding a port request.
Not every extension ever, but every extension that a current MacPorts user wants to use? Sure, why not? That's what MacPorts is here for: to provide and easy means to install and manage software on OS X.
I have a relatively fresh macport I moved the php-config.1.gz man files and got php5 to activate.
Great!
comment:4 Changed 11 years ago by veltenheyn@…
Replying to ryandesign@…:
php5 doesn't provide pecl or pear either, does it?
It does install pecl, pear, peardev into /opt/local/bin/
comment:5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
...oh, you must've selected the +pear variant of php5. It doesn't normally do that.
Why do you need to run pecl manually, and why do you think you need the php5 port to do so -- why is the php55 port insufficient for that? If there is a php module you need that does not have a port in MacPorts, please file a port request ticket so that we can add it to MacPorts.
"port contents php55" should not list php-config.1.gz. It should list php-config55.1.gz. Please verify. php5 should not conflict with php55, and does not on my system.
MacPorts says php-config.1.gz already exists and does not belong to a registered port. You're the only one who can explain why that might be so. You can force the activation of php5 if you like, but if you have rogue php5 files on your system already, who knows how many other rogue files you have.
Note that php5 is the "old" MacPorts php world from years ago and is deprecated and will eventually be removed. php53, php54, php55, php56 is the "new" php world which you should be using instead.