On Tue, Aug 9, 2011 at 02:31, Russell Jones <[email protected]>wrote:
> > If so, I would be strongly against that. "port select" is exclusively for > a user's convenience; no port should change how it installs or functions > based on what the user may or may not have "port select"ed. > > I can kind of see why you wouldn't want this on principle, but could you > elaborate? Why should a user have to select which version of python they > want for every package, when in the majority of cases the same version will > be desired? Having a default doesn't exclude exceptions. > When the user uses port select to change the default Python, what should happen to all of these? How do you plan to implement it? What if there isn't a version of something installed this way for the selected Python variant? -- brandon s allbery [email protected] wandering unix systems administrator (available) (412) 475-9364 vm/sms
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
