From: jnbr <jnbr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Miniflux hard postgresql dependency
Date: Mon, 05 Oct 2020 01:13:02 +0200 [thread overview]
Message-ID: <20201004231302.dWctU0ZPmP2AhALMxlQKPtqNHtYv-xKlULaa2jkqhEk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25342@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
New comment by jnbr on void-packages repository
https://github.com/void-linux/void-packages/issues/25342#issuecomment-703329678
Comment:
While it is true that miniflux needs a postgresql database, the specific version does not matter and there is also no need for it to be on the same host as miniflux itself.
I think the simpler and better solution in this case is to make miniflux not depend on postgresql.
This way, we can avoid all the pitfalls virtual packages come with.
next prev parent reply other threads:[~2020-10-04 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 18:17 [ISSUE] " chilledfrogs
2020-10-04 19:08 ` ahesford
2020-10-04 23:13 ` jnbr [this message]
2020-10-06 17:44 ` [ISSUE] [CLOSED] " jnbr
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=20201004231302.dWctU0ZPmP2AhALMxlQKPtqNHtYv-xKlULaa2jkqhEk@z \
--to=jnbr@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).