[MacPorts] #36558: ssss @1.0.1

MacPorts noreply at macports.org
Sat Oct 13 02:08:12 PDT 2012


#36558: ssss @1.0.1
-------------------------+--------------------------
  Reporter:  okoeroo@…   |      Owner:  ryandesign@…
      Type:  submission  |     Status:  closed
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.1.2
Resolution:  fixed       |   Keywords:
      Port:  ssss        |
-------------------------+--------------------------

Comment (by okoeroo@…):

 Replying to [comment:7 ryandesign@…]:
 > Thanks. Committed in r98694 with some changes. Since the bootstrap
 script is still running programs provided by the autoconf, automake and
 libtool ports, I added those dependencies to depends_build.
 ("use_autoreconf yes" had added them for you automatically, so when you
 removed that line it became your responsibility to add those dependencies
 yourself.) I also used the Tcl "file mkdir" command to make the project
 directory; no need to launch a separate program to do that.
 >
 > With regard to the updated checksums, I see this is because you
 incorporated a fix to an issue I filed and re-tagged 1.0.1. Please avoid
 re-tagging your releases in the future. We call this a
 [wiki:PortfileRecipes#stealth-updates stealth update] and we discourage
 it. Imagine what would have happened if we had accepted your 1.0.1
 portfile as originally submitted (imagine we had figured out we needed to
 create the "project" directory and had included that directive in the
 portfile). Then two days later you re-tagged 1.0.1, thus changing the
 checksums. Now some users trying to install the port (those for whom the
 github server is closer than any MacPorts mirror server) will encounter a
 [wiki:FAQ#checksums checksum mismatch error], which will inconvenience the
 user and will occupy our time when we have to deal with the bug report the
 user will undoubtedly file. Therefore once you've created a tag or release
 please consider it to be immutable. If you need to make further changes
 and publish them to your users, do so under a new version number.

 Thanks for the fixes. I'm aware of my retagging action to be dangerous. As
 MacPorts is going to be the first one to really be hit by this I've took
 the liberty just this once to retag it fully understanding the potential
 impact of messing up the Port for others if I would do this again.

-- 
Ticket URL: <https://trac.macports.org/ticket/36558#comment:9>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list