On May 18, 2010, at 5:51 AM, Ryan Schmidt wrote:
On May 18, 2010, at 07:04, Bradley Giesbrecht wrote:
Maybe local repos is something that should be promoted and made
more prominent on the homepage and in the guide?
Personally I've never used a local port repository, don't need one,
and don't think regular users should need one either. It seems like
it would just promote the practice of users solving problems on
their own and not contributing back to the community when they can
just shove a file in a folder and it works for them so they move on
to the next problem, rather than helping us fix the problem at the
source.
This comment almost makes me mad. The handful committers don't need
local repos. Wonder why?
For example, if I didn't want "port upgrade outdated" to upgrade
openssl I could copy the openssl port to a local repo and have
something similar to package masks on gentoo.
I would rather like for there to be no reason for the user to want
to do that. Again, if the user has easy access to a way to install
the older version of a port, then they don't report to us the
problems they experienced with the current version, which is bad for
the project.
When openssl was upgraded to v1 beta or what ever and it broke
everything I care about it made me wish for a way to stop port from
upgrading things I didn't ask it to.
On gentoo gcc would be updated pretty frequently and a lot of people,
myself included, didn't want to recompile gcc every other week.
// Brad
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
