I think we might possibly be talking past each other - let me rephrase my concerns about the EXPLICIT_PACKAGE_DEPENDS switch and its functionality:
- I am concerned about users trying to use that switch *now* to cut down time on portupgrade -r and portupgrade -R operations and getting inconsistently updated installations as a result. That was the main motivation for my initial reply to your message - since there is no documentation other than your messages for that switch and since it does not print out any warnings either, I thought I had to issue that warning. Other than that, I realise this is experimental and off by default and as such I don't have a problem with it. Providing the missing documentation and make the switch print appropriate warnings might still be worthwhile though. - I am also concerned about this switch or its functionality becoming the default before all ports are sufficiently modified (all dependencies listed) so the scenario I describe above will not occur. Portmgr's call though. - Finally, I am concerned about the amount of work required to keep the dependencies up to date. This last concern is admittedly KDE-centric (and thus selfish :). The more automated tests or automated dependency registration mechanisms there are in place, the less concern there will be from my side. Those two quickshots already look pretty good - how about trying to integrate them into the pointyhat buildscript? Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
signature.asc
Description: OpenPGP digital signature
