On Nov 13, 2011, at 23:56, Joshua Root wrote: > On 2011-11-14 16:38 , Ryan Schmidt wrote: >> >> I wasn't sure what would happen when you change the case of the port name >> like that. Will users who had qlipper @1.8.2_0 installed get prompted to >> upgrade to Qlipper @1.8.2_1? I don't think this is a case we ever >> deliberately considered, so if it does work, it probably works by >> coincidence (though I'm not opposed to making this a supported kind of >> change). > > It works very much by design. Remember > <https://trac.macports.org/ticket/11759>?
I absolutely remember. That ticket was about giving the user the freedom to type port names case-insensitively, and port would recognize what the correct case was and always install and uninstall the port with the right case. Clearly something (subports?) has broken this somewhat in MacPorts 2 as described in <https://trac.macports.org/ticket/31743> . And it was never clear to me that MacPorts knows what "the correct case" is if that differs between the previously installed port and the newly installed port. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
