[MacPorts] #44927: s3cmd @1.0.1 update to 1.5.0-rc1
#44927: s3cmd @1.0.1 update to 1.5.0-rc1 ------------------------+-------------------------------- Reporter: rockettj@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: ------------------------+-------------------------------- Bump to the latest release. -- Ticket URL: <https://trac.macports.org/ticket/44927> MacPorts <http://www.macports.org/> Ports system for OS X
#44927: s3cmd @1.0.1 update to 1.5.0-rc1 -------------------------+-------------------------------- Reporter: rockettj@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: s3cmd | -------------------------+-------------------------------- Changes (by mf2k@…): * cc: rockettj@… (removed) * version: 2.3.1 => * port: => s3cmd Comment: Thanks. In the future, please fill in the Port field. As reporter, you do not need to Cc yourself. Some comments: - The {{{revision}}} line should be deleted because it starts at 0 when increasing the version and that is the default value. - Use a sha256 checksum and remove the obsolete sha1 and md5 checksums unless upstream provides them. -- Ticket URL: <https://trac.macports.org/ticket/44927#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#44927: s3cmd @1.0.1 update to 1.5.0-rc1 -------------------------+-------------------------------- Reporter: rockettj@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: s3cmd | -------------------------+-------------------------------- Comment (by mf2k@…): - And most importantly, we do not normally use rc versions. We like to use stable release versions. If this were a -devel port, then it could use that version. -- Ticket URL: <https://trac.macports.org/ticket/44927#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#44927: s3cmd @1.0.1 update to 1.5.0-rc1 -------------------------+-------------------------------- Reporter: rockettj@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: s3cmd | -------------------------+-------------------------------- Comment (by rockettj@…): Ok, thanks for the comments. I'll make the corrections. -- Ticket URL: <https://trac.macports.org/ticket/44927#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#44927: s3cmd @1.0.1 update to 1.5.0-rc1 -------------------------+-------------------------------- Reporter: rockettj@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: s3cmd | -------------------------+-------------------------------- Comment (by ryandesign@…): Each distfile should be validated by at least two different checksum types. Usually we use rmd160 and sha256. But yes, we should wait to update this port until a new official release is available. 1.5.0-rc1 is not an official release, it is a ''r''elease ''c''anditate. The latest official release still seems to be 1.0.1. -- Ticket URL: <https://trac.macports.org/ticket/44927#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#44927: s3cmd @1.0.1 update to 1.5.0-rc1 -------------------------+-------------------------------- Reporter: rockettj@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: s3cmd | -------------------------+-------------------------------- Comment (by mf2k@…): Yes, sorry for the confusion. I implied, but did not state explicitly, that the rmd160 checksum needs to stay. -- Ticket URL: <https://trac.macports.org/ticket/44927#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#44927: s3cmd @1.0.1 update to 1.5.0-rc1 -------------------------+-------------------------------- Reporter: rockettj@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: s3cmd | -------------------------+-------------------------------- Comment (by rockettj@…): Thanks for your patience (my first submittal here). Should I close and reopen to add a s3cmd-devel or is ok to wait and update this ticket once 1.5.0 is released? I'll add the rmd160 back in. -- Ticket URL: <https://trac.macports.org/ticket/44927#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
#44927: s3cmd @1.0.1 update to 1.5.0-rc1 -------------------------+-------------------------------- Reporter: rockettj@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: s3cmd | -------------------------+-------------------------------- Comment (by mf2k@…): It would be easiest to simply wait for the final 1.5.0 release. If you think that a s3cmd-devel is useful going forward, then it would be best to modify the current s3cmd port and add it as a sub-port. -- Ticket URL: <https://trac.macports.org/ticket/44927#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts