Bug 340229 – dev-lang/php-5.3.3-r2 breaks path to php binary

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Stevan Bajić 2010-10-09 08:29:50 UTC]

Installing dev-lang/php-5.3.3-r2 breaks paths to the php binary. Executing just "php" on the command line (when having PHP with cli use flag) results in a "ommand not found" error. The Ebuild does not set the symlink for /usr/bin/php as well. So all other Ebuilds requiring the php binary will fail too.

Reproducible: Always

[Comment 1 Ole Markus With (RETIRED) 2010-10-09 11:02:08 UTC]

The problem is that eselect-php doesn't properly validate symlinks so it thinks that the symlink left behind by php-toolkit is still valid.

You should be able to solve the problem using `eselect php cli set php5.3`

[Comment 2 Stevan Bajić 2010-10-09 11:09:00 UTC]

(In reply to comment #1)
> The problem is that eselect-php doesn't properly validate symlinks so it thinks
> that the symlink left behind by php-toolkit is still valid.
> 
> You should be able to solve the problem using `eselect php cli set php5.3`
> 

Right. Using `eselect php set cli php5.3` solved the issue. IMHO the ebuild should either do it or print out instructions that this command is needed.

[Comment 3 Ole Markus With (RETIRED) 2010-10-09 11:56:39 UTC]

(In reply to comment #2)
> (In reply to comment #1)
> > The problem is that eselect-php doesn't properly validate symlinks so it thinks
> > that the symlink left behind by php-toolkit is still valid.
> > 
> > You should be able to solve the problem using `eselect php cli set php5.3`
> > 
> 
> Right. Using `eselect php set cli php5.3` solved the issue. IMHO the ebuild
> should either do it or print out instructions that this command is needed.
> 

Of course. It should. But then, this package is p.masked, which means it doesn't do what it is supposed to do yet. Anyways, a fix to the broken eblit has been commited to the tree and a fix to the eselect module is available in the php overlay.

Will close this when the fixed eselect module also hits the tree.

[Comment 4 H. Peter Pfeufer 2010-10-11 10:31:08 UTC]

(In reply to comment #1)
> The problem is that eselect-php doesn't properly validate symlinks so it thinks
> that the symlink left behind by php-toolkit is still valid.
> 
> You should be able to solve the problem using `eselect php cli set php5.3`
> 

So i have this error when i try eselect

eselect php cli set php5.3
!!! Error: Action cli unknown
exiting

[Comment 5 Ole Markus With (RETIRED) 2010-10-11 11:08:14 UTC]

What do you (In reply to comment #4)
> (In reply to comment #1)
> > The problem is that eselect-php doesn't properly validate symlinks so it thinks
> > that the symlink left behind by php-toolkit is still valid.
> > 
> > You should be able to solve the problem using `eselect php cli set php5.3`
> > 
> 
> So i have this error when i try eselect
> 
> eselect php cli set php5.3
> !!! Error: Action cli unknown
> exiting
> 

Where did you see that order of arguments?
It should be `eselect php *set* *cli* php5.3`. You have those the other way around.

[Comment 6 H. Peter Pfeufer 2010-10-11 11:37:44 UTC]

(In reply to comment #5)
> 
> Where did you see that order of arguments?
> It should be `eselect php *set* *cli* php5.3`. You have those the other way
> around.
> 

Comment #1

Thanks so far

[Comment 7 Stevan Bajić 2010-10-11 14:40:54 UTC]

(In reply to comment #6)
> (In reply to comment #5)
> > 
> > Where did you see that order of arguments?
> > It should be `eselect php *set* *cli* php5.3`. You have those the other way
> > around.
> > 
> 
> Comment #1
> 
> Thanks so far
> 

Comment #2 has the right order.

[Comment 8 Stevan Bajić 2010-10-11 14:43:40 UTC]

(In reply to comment #3)

> Of course. It should. But then, this package is p.masked, which means it
> doesn't do what it is supposed to do yet.
>
You are right but being p.masked does not mean it should be left broken. The goal is IMHO to get any Ebuild to be error free (as much as possible).

[Comment 9 Ole Markus With (RETIRED) 2010-10-19 20:09:46 UTC]

Does this work for you now?

[Comment 10 Stevan Bajić 2010-10-20 05:32:52 UTC]

(In reply to comment #9)
> Does this work for you now?
> 
With "this" you mean the eselect command? Yes. The eselect command works. Not perfectly but it works. Not perfect in that sense that I had ebuilds where I needed to create a symlink from /usr/bin/php to /usr/bin/php5.3 in order to be able to emerge them.

[Comment 11 Ole Markus With (RETIRED) 2010-10-20 05:35:59 UTC]

(In reply to comment #10)
> (In reply to comment #9)
> > Does this work for you now?
> > 
> With "this" you mean the eselect command? Yes. The eselect command works. Not
> perfectly but it works. Not perfect in that sense that I had ebuilds where I
> needed to create a symlink from /usr/bin/php to /usr/bin/php5.3 in order to be
> able to emerge them.

With "this" I mean that the PHP ebuild runs eselect if the symlinks are either broken or does not exist. Beats me why you need a symlink to /usr/bin/php5.3 ...

[Comment 12 Stevan Bajić 2010-10-20 06:08:03 UTC]

(In reply to comment #11)
> (In reply to comment #10)
> > (In reply to comment #9)
> > > Does this work for you now?
> > > 
> > With "this" you mean the eselect command? Yes. The eselect command works. Not
> > perfectly but it works. Not perfect in that sense that I had ebuilds where I
> > needed to create a symlink from /usr/bin/php to /usr/bin/php5.3 in order to be
> > able to emerge them.
> 
> With "this" I mean that the PHP ebuild runs eselect if the symlinks are either
> broken or does not exist.
>
aha. Have not tested re-emerged PHP after this initial bug report. Will do that after getting back from work.


> Beats me why you need a symlink to /usr/bin/php5.3
> ...
> 
It was PEAR or a PEAR related ebuild. Need to check out which one it was. Will keep you up to date later.

[Comment 13 Ole Markus With (RETIRED) 2010-10-30 17:33:35 UTC]

This one should work as expected now