Github messages for voidlinux
 help / color / mirror / Atom feed
From: IcedQuinn <IcedQuinn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] minio
Date: Mon, 15 Nov 2021 04:28:54 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34089@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 913 bytes --]

New issue by IcedQuinn on void-packages repository

https://github.com/void-linux/void-packages/issues/34089

Description:
The package seems to be out of date but also subtly broken.

There is a post-install note on the console to edit a config json file. This config json file is no longer used by the version of minio (it replaces the file with a .deprecated and seemingly ignores it) which is presently packaged.

To complicate things further there has been a license+big GUI change in Minio. It has gone from Apache to AGPL which may be bothersome to some users.

Some action items to consider:
- Post-install script should not point user toward config files that appear to no longer be used
- Is a major license change needing ex. renaming the package to avoid accidental crossgrading
- What to do about minio preferring ex. access keys be passed in environment variables instead of the config.json

             reply	other threads:[~2021-11-15  3:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15  3:28 IcedQuinn [this message]
2021-11-24  0:23 ` minio dotnetfox
2021-11-29 19:22 ` minio arete
2022-06-13  2:16 ` minio github-actions
2022-06-28  2:15 ` [ISSUE] [CLOSED] minio github-actions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34089@inbox.vuxu.org \
    --to=icedquinn@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).