What I like to know (I can of course file a ticket, but that gives me no way of
knowing when it happens, so I prefer to do the update myself, test it and then
produce a pull request)
The Portfile contains:
> # UPDATE THESE IN SYNC!
> set version 2019-09-11T19-53-16Z
> set commit 53e4887e02b94ed37dea8c5173330f17548fe122
>
> set relversion [regsub {(T..)-(..)-(..Z)} $version {\1:\2:\3}]
> # This is not used for fetching, but is compiled into the executable
>
> github.setup minio minio $version RELEASE.
> revision 0
>
> homepage https://minio.io
> categories www
> maintainers {eborisch @eborisch} openmaintainer
> description Open source Amazon S3-compatible object storage server.
> long_description \
> ${description} It is best suited for storing unstructured data such as \
> photos, videos, log files, backups and container / VM images. Size of an \
> object can range from a few KBs to a maximum of 5TB. See also minio-mc \
> for command-line client.
> license Apache-2
>
> checksums \
> rmd160 538b2615c7e043562b74d619e28e608adbafbdf2 \
> sha256 abfc96e02d1fed4fc0b3dd3e12885bf79e9bc3b33b42bd2fa0ae1023d58fc714 \
> size 6955992
I can find out what the set for version (github.com/minio/minio says
RELEASE.2020-01-25T02-50-51Z)
But what is to be put in ’set commit’ and where can I find it?
I can then perform a fetch and calculate the checksums and I should be ready to
go, right?
It looks to me (am I right?) with the set commit statement that direct access
to github is used instead of downloading a tar somewher. E.g. compare postfix:
> version 3.4.8
> categories mail
> license {IBMPL-1 EPL-2}
> maintainers {jmr @jmroot} openmaintainer
> description Fast and robust mail transfer agent
> long_description Postfix attempts to be fast, easy to administer, and \
> secure, while at the same time being \
> sendmail-compatible enough to not upset existing \
> users. It also offers QMQP and VERP support to let \
> Postfix act as delivery daemon for ezmlm-idx.
> homepage http://www.postfix.org/
> platforms darwin
> checksums rmd160 430c5294a1fd4ca5411e13fb328897e01a03a055 \
> sha256
> 8d5d429737e0c64514028a82fc006cbb273d2cb98dc40eb1dbbfe102f29a8943
>
> master_sites https://archive.mgm51.com/mirrors/postfix-source/official/ \
> http://de.postfix.org/ftpmirror/official/ \
>
> ftp://ftp.its.cz/MIRRORS/ftp.porcupine.org/mirrors/postfix-release/official/ \
>
> ftp://ftp.cuhk.edu.hk/pub/packages/mail-server/postfix/official/ \
> http://mirror.postfix.jp/postfix-release/official/ \
> http://postfix.bbnx.net/source/official/ \
>
> http://cdn.postfix.johnriley.me/mirrors/postfix-release/official/
So, these Portfiles look pretty different and it is not clear to me how to
update the MinIO one. For postfix, it is enough to change the version and fetch
But it is not so for the MinIO one.
Yours,
Gerben Wierda
Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/>
Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>
Architecture for Real Enterprises
<https://www.infoworld.com/blog/architecture-for-real-enterprises/> at InfoWorld
On Slippery Ice <https://eapj.org/on-slippery-ice/> at EAPJ
> On 27 Jan 2020, at 09:27, Ryan Schmidt <[email protected]> wrote:
>
>
>
> On Jan 25, 2020, at 08:34, Gerben Wierda wrote:
>
>> How do I update the MinIo Portfile so it fetches and compiles
>> RELEASE.2020-01-25T02-50-51Z?
>>
>> This is different from source .tar.gz downloads and such and I cannot find
>> instructions on how to do this.
>
> Not sure what you mean. The MinIO Portfile does download a .tar.gz.
>
> The port has a long history. You can look at it on GitHub:
>
> https://github.com/macports/macports-ports/commits/master/www/minio/Portfile
>
> You can see how previous updates were performed. Here is the most recent:
>
> https://github.com/macports/macports-ports/commit/bec9373f900ef6dcee6c40946933f3f3952bbdb6
>
> Also, the port has a maintainer, so you can just file a ticket asking them to
> update the port.
>
