public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: libloc 0.9.15 released
Date: Mon, 26 Sep 2022 16:52:03 +0100	[thread overview]
Message-ID: <D7B6462F-CC08-4F1A-AD59-A8EE35C6F08A@ipfire.org> (raw)

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

Hello,

This is the release announcement for libloc 0.9.15. It comes with the following changes:

* Major refactoring of the code that maps the database into memory has been undertaken. This is to support any architectures that do not have a page size of four kilobytes. Instead mapping individual parts of the database, the entire file is being mmapped into memory which removes the earlier restriction.

* The library is telling the kernel that it intends to randomly read data from the file, which results in a minor performance improvement on slower storage devices.

* The testsuite has been extended and we now check for better return codes in case the database could not be opened.

* The library compiles on Mac OS X again - but support is not yet ready for production.

* The configure script now understands the —with-database-path switch which can be used to set an alternative path for the database.

* The location Python module has a new function called “open” which called without an argument tries to open the default database, and if called with a path argument will open the database at the given path.

Thank you to everyone who has contributed to this release.

You can find the source here:

https://git.ipfire.org/?p=location/libloc.git;a=shortlog;h=refs/tags/0.9.15
https://source.ipfire.org/releases/libloc/libloc-0.9.15.tar.gz

Best,
-Michael

                 reply	other threads:[~2022-09-26 15:52 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=D7B6462F-CC08-4F1A-AD59-A8EE35C6F08A@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