svn commit: r364287 - head/ports-mgmt/pkg-devel

[Bryan Drewery]

On 2014-08-11 02:07, Max Brazhnikov wrote:
> On Sun, 10 Aug 2014 23:24:16 +0100 Matthew Seaman wrote:
>> On 10/08/2014 21:09, Vsevolod Stakhov wrote:
>> > Nonetheless, doesn't our ports policy defines to bump PORTREVISION in
>> > all cases that modifies a resulting package? Shlib provides/requires
>> > changing is definitely such a change. So you blame now pkg that it
>> > follows the current policy, don't you?
>> 
>> Bumping PORTREVISION in this situation is the standard policy only
>> because we previously lacked the tools to update dependent ports on
>> shlib ABI changes without it.
>> 
>> Ideally, pkg(8) will be able to make that policy obsolete by 
>> automating
>> away the manual reverse-dependency tracking that should be (but is not
>> always) being done at the moment.
> 
> It won't work in all cases anyway. I can give examples of ports, that 
> must be
> rebuilt if dependency gets updated, and it's not related to shared 
> libraries.

PHP extensions are like this. Must be rebuilt on every PHP version bump 
- and reinstalled. Currently pkg does not recognize this, and committers 
are not bumping revisions either. It would require bumping all PHP 
extension ports. Including non-obvious ones such as devel/ioncube, 
devel/eaccelerator.

-- 
Regards,
Bryan Drewery