From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: How to update the database daily?
Date: Wed, 02 Oct 2019 11:47:56 +0100 [thread overview]
Message-ID: <216FB4E0-CB79-4542-BEDB-8CF0B3DE18CE@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
Hello,
I just wanted to summarise and archive a conversation that I had with Peter yesterday on the phone:
We were talking about what mechanisms would be best to distribute the database on a daily basis. There are two options of which the first one is a downloader script which is called by systemd or cron on a regular basis, downloads the database, verifies it and done.
The second option is to use the package updating mechanism of distributions, i.e. sending a daily update of a package with the latest version of the database. That way, no extra configuration for systems behind a proxy and without any access to the internet would be necessary.
I personally do not think that any distribution would be able or willing to push a daily package update regardless of its size. There is no precedent for it in any distribution I know, but Peter was going to check with Debian if this is a possible path and report back.
Best,
-Michael
reply other threads:[~2019-10-02 10:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=216FB4E0-CB79-4542-BEDB-8CF0B3DE18CE@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=location@lists.ipfire.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