Re: [33525] trunk/dports/python/py25-gsl/Portfile
On Jan 29, 2008, at 01:21, jmpp@macports.org wrote:
Revision: 33525 http://trac.macosforge.org/projects/macports/changeset/33525 Author: jmpp@macports.org Date: 2008-01-28 23:21:25 -0800 (Mon, 28 Jan 2008)
Log Message: -----------
Change portname to py25-gsl, as it should have been from the start.
To all committers: when using a given port as the basis of a new one, please always remember to make sure you adapt the portname for the latter, as having duplicate portname entries in our tree is not allowed (not only does it mess up informational operations, but it could also wreck havoc for a user that somehow manages to install the two colliding ports).
Yes, I'm aware we don't have strong checks against this harmful situation within MacPorts' base, and I'm also aware that we should... But, as we currently don't, let warnings like this raise committers' awareness of the issue, while we develop a *real* solution.
Yeah. A good solution would already be: * "port lint" should issue a warning for this: http://trac.macosforge.org/projects/macports/ticket/13263 * "port lint" should be run by the Subversion repository in a post- commit hook and any problems found emailed to the committer and the maintainer: http://trac.macosforge.org/projects/macports/ticket/12594#comment:4
I can add `port lint` to the post-commit for any Portfiles if you want. I dont see a way to get only the list of maintainers from port, but I can always grep/regexp to get them from `port info`? I seem to remember a better way though. -Bill On Jan 29, 2008, at 6:29 AM, Ryan Schmidt wrote:
On Jan 29, 2008, at 01:21, jmpp@macports.org wrote:
Revision: 33525 http://trac.macosforge.org/projects/macports/changeset/33525 Author: jmpp@macports.org Date: 2008-01-28 23:21:25 -0800 (Mon, 28 Jan 2008)
Log Message: -----------
Change portname to py25-gsl, as it should have been from the start.
To all committers: when using a given port as the basis of a new one, please always remember to make sure you adapt the portname for the latter, as having duplicate portname entries in our tree is not allowed (not only does it mess up informational operations, but it could also wreck havoc for a user that somehow manages to install the two colliding ports).
Yes, I'm aware we don't have strong checks against this harmful situation within MacPorts' base, and I'm also aware that we should... But, as we currently don't, let warnings like this raise committers' awareness of the issue, while we develop a *real* solution.
Yeah. A good solution would already be:
* "port lint" should issue a warning for this:
http://trac.macosforge.org/projects/macports/ticket/13263
* "port lint" should be run by the Subversion repository in a post- commit hook and any problems found emailed to the committer and the maintainer:
http://trac.macosforge.org/projects/macports/ticket/12594#comment:4
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
---- William Siegrist Software Support Engineer Mac OS Forge http://macosforge.org/ wsiegrist@apple.com 408 862 7337
participants (2)
-
Ryan Schmidt
-
William Siegrist