On Aug 13, 2013, at 8:13 PM, Clemens Lang <c...@macports.org> wrote: > On Tue, Aug 13, 2013 at 06:55:25PM -0500, Ryan Schmidt wrote: >> I don't know but it seems useful in the following scenario: […] > > I agree there's a use-case for this behavior, but I can just aswell > provide a use-case that is broken by this behavior: > - (Work on an upgrade for port foo) > - (Test this upgrade by) running the installation up to (including) the > archiving: sudo port archive foo > - (Commit the change to foo) > - (Run portindex) > - Run port upgrade outdated > -> foo isn't upgraded.
The brokenness of this use case seems to mainly inconvenience MacPorts developers, whereas breaking Ryan's use case could be a hassle for MacPorts users. vq _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
