Status of portupgrade and portmaster?

[abi]

02.10.2017 13:25, Matt Smith пишет:
> On Oct 02 12:05, Vlad K. wrote:
>> On 2017-10-02 11:57, abi wrote:
>>> 2. Dependency chain is not updated - if I disable B feature on port A,
>>> poudriere asks me for options of ports implementing B. I have to
>>> Ctrl+C after any option change.
>>
>>
>> I find that annoying as well, but.... isn't that just how the 
>> config-recursive ports framework target works? Poudriere is really 
>> using the ports make targets here.
>>
>> Do synth or portmaster do it differently?
>>
>
> Synths philosophy was that you should have the absolute bare minimum 
> of options set and John wrote a script to do just this in 
> /usr/ports/Tools/scripts/redundant-opt-files.sh to delete any which 
> just have defaults in them.
>
The thing John doesn't explain why we need to purge "redundant options". 
They are not redundant, they inform user that port options are not 
changed after ports tree update. Synth softly suggests user *not* to 
change ports options, because it's hard to manage them and stay in synth 
"philosophy".