py-twistedweb2 and py25-twisted-web2 uses different name convension
Hi, I noticed that twisted for python2.4 and 2.5 uses different name convension. I opened new ticket http://trac.macosforge.org/projects/macports/ticket/14375 Shouldn' they use the same convension?
On Feb 29, 2008, at 09:20, js wrote:
I noticed that twisted for python2.4 and 2.5 uses different name convension. I opened new ticket http://trac.macosforge.org/projects/macports/ ticket/14375
Shouldn' they use the same convension?
Sure, it would make sense for the common parts of the port name to be the same.
The problem is this breaks the upgrade path. Anybody with py25-twisted- web2 will lose the ability to update their port if it gets renamed to py25-twistedweb2. They'll have to discover this problem on their own and uninstall py25-twisted-web2 and install py25-twistedweb2. The only workaround I can think of for this is to push a dummy update for py25-twisted-web2 that errors out on fetch with a message saying to uninstall and reinstall py25-twistedweb2, but that's ugly and unfriendly. -Kevin Ballard On Feb 29, 2008, at 3:28 PM, Ryan Schmidt wrote:
On Feb 29, 2008, at 09:20, js wrote:
I noticed that twisted for python2.4 and 2.5 uses different name convension. I opened new ticket http://trac.macosforge.org/projects/macports/ticket/14375
Shouldn' they use the same convension?
Sure, it would make sense for the common parts of the port name to be the same.
-- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com
On Feb 29, 2008, at 14:33, Kevin Ballard wrote:
On Feb 29, 2008, at 3:28 PM, Ryan Schmidt wrote:
On Feb 29, 2008, at 09:20, js wrote:
I noticed that twisted for python2.4 and 2.5 uses different name convension. I opened new ticket http://trac.macosforge.org/projects/macports/ ticket/14375
Shouldn' they use the same convension?
Sure, it would make sense for the common parts of the port name to be the same.
The problem is this breaks the upgrade path. Anybody with py25- twisted- web2 will lose the ability to update their port if it gets renamed to py25-twistedweb2. They'll have to discover this problem on their own and uninstall py25-twisted-web2 and install py25-twistedweb2.
The only workaround I can think of for this is to push a dummy update for py25-twisted-web2 that errors out on fetch with a message saying to uninstall and reinstall py25-twistedweb2, but that's ugly and unfriendly.
Still wish we had the "superseded_by" feature in MacPorts base so it would be easier to rename a port: http://lists.macosforge.org/pipermail/macports-dev/2007-July/002219.html http://lists.macosforge.org/pipermail/macports-dev/2007-December/ 003767.html
Then, is my request rejected? Who has the power to decide this kind of issue? On Sat, Mar 1, 2008 at 6:07 AM, Ryan Schmidt <ryandesign@macports.org> wrote:
On Feb 29, 2008, at 14:33, Kevin Ballard wrote:
On Feb 29, 2008, at 3:28 PM, Ryan Schmidt wrote:
On Feb 29, 2008, at 09:20, js wrote:
I noticed that twisted for python2.4 and 2.5 uses different name convension. I opened new ticket http://trac.macosforge.org/projects/macports/ ticket/14375
Shouldn' they use the same convension?
Sure, it would make sense for the common parts of the port name to be the same.
The problem is this breaks the upgrade path. Anybody with py25- twisted- web2 will lose the ability to update their port if it gets renamed to py25-twistedweb2. They'll have to discover this problem on their own and uninstall py25-twisted-web2 and install py25-twistedweb2.
The only workaround I can think of for this is to push a dummy update for py25-twisted-web2 that errors out on fetch with a message saying to uninstall and reinstall py25-twistedweb2, but that's ugly and unfriendly.
Still wish we had the "superseded_by" feature in MacPorts base so it would be easier to rename a port:
http://lists.macosforge.org/pipermail/macports-dev/2007-July/002219.html
http://lists.macosforge.org/pipermail/macports-dev/2007-December/ 003767.html
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
BTW, Twisted Web2 is still under development and recommend using svn trunk until next release. So I assume there're not so many people using twisted web2 port. I think now is the time to fix this portname. On Tue, Mar 4, 2008 at 9:27 PM, js <ebgssth@gmail.com> wrote:
Then, is my request rejected? Who has the power to decide this kind of issue?
On Sat, Mar 1, 2008 at 6:07 AM, Ryan Schmidt <ryandesign@macports.org> wrote:
On Feb 29, 2008, at 14:33, Kevin Ballard wrote:
On Feb 29, 2008, at 3:28 PM, Ryan Schmidt wrote:
On Feb 29, 2008, at 09:20, js wrote:
I noticed that twisted for python2.4 and 2.5 uses different name convension. I opened new ticket http://trac.macosforge.org/projects/macports/ ticket/14375
Shouldn' they use the same convension?
Sure, it would make sense for the common parts of the port name to be the same.
The problem is this breaks the upgrade path. Anybody with py25- twisted- web2 will lose the ability to update their port if it gets renamed to py25-twistedweb2. They'll have to discover this problem on their own and uninstall py25-twisted-web2 and install py25-twistedweb2.
The only workaround I can think of for this is to push a dummy update for py25-twisted-web2 that errors out on fetch with a message saying to uninstall and reinstall py25-twistedweb2, but that's ugly and unfriendly.
Still wish we had the "superseded_by" feature in MacPorts base so it would be easier to rename a port:
http://lists.macosforge.org/pipermail/macports-dev/2007-July/002219.html
http://lists.macosforge.org/pipermail/macports-dev/2007-December/ 003767.html
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
More people apparently agreed this change. I attached the fix below. http://trac.macosforge.org/projects/macports/ticket/14375 Closing this discussion. On Sat, Mar 8, 2008 at 1:55 PM, js <ebgssth@gmail.com> wrote:
BTW, Twisted Web2 is still under development and recommend using svn trunk until next release. So I assume there're not so many people using twisted web2 port. I think now is the time to fix this portname.
On Tue, Mar 4, 2008 at 9:27 PM, js <ebgssth@gmail.com> wrote:
Then, is my request rejected? Who has the power to decide this kind of issue?
On Sat, Mar 1, 2008 at 6:07 AM, Ryan Schmidt <ryandesign@macports.org> wrote:
On Feb 29, 2008, at 14:33, Kevin Ballard wrote:
On Feb 29, 2008, at 3:28 PM, Ryan Schmidt wrote:
On Feb 29, 2008, at 09:20, js wrote:
I noticed that twisted for python2.4 and 2.5 uses different name convension. I opened new ticket http://trac.macosforge.org/projects/macports/ ticket/14375
Shouldn' they use the same convension?
Sure, it would make sense for the common parts of the port name to be the same.
The problem is this breaks the upgrade path. Anybody with py25- twisted- web2 will lose the ability to update their port if it gets renamed to py25-twistedweb2. They'll have to discover this problem on their own and uninstall py25-twisted-web2 and install py25-twistedweb2.
The only workaround I can think of for this is to push a dummy update for py25-twisted-web2 that errors out on fetch with a message saying to uninstall and reinstall py25-twistedweb2, but that's ugly and unfriendly.
Still wish we had the "superseded_by" feature in MacPorts base so it would be easier to rename a port:
http://lists.macosforge.org/pipermail/macports-dev/2007-July/002219.html
http://lists.macosforge.org/pipermail/macports-dev/2007-December/ 003767.html
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
participants (3)
-
js
-
Kevin Ballard
-
Ryan Schmidt