Date: Fri, 2 Mar 2012 18:47:43 +0000 (UTC) From: Jason Helfman <jgh@FreeBSD.org> To: ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: ports/security/py-keyring Makefile distinfo pkg-plist Message-ID: <201203021847.q22Ilhup090588@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
jgh 2012-03-02 18:47:43 UTC FreeBSD ports repository Modified files: security/py-keyring Makefile distinfo pkg-plist Log: -Update to 0.8 * Mac OS X keyring backend now uses subprocess calls to the `security` command instead of calling the API, which with the latest updates, no longer allows Python to invoke from a virtualenv. Fixes issue #13. * When using file-based storage, the keyring files are no longer stored in the user's home directory, but are instead stored in platform-friendly locations (`%localappdata%\Python Keyring` on Windows and according to the freedesktop.org Base Dir Specification (`$XDG_DATA_HOME/python_keyring` or `$HOME/.local/share/python_keyring`) on other operating systems). This fixes #21. *Backward Compatibility Notice* Due to the new storage location for file-based keyrings, keyring 0.8 supports backward compatibility by automatically moving the password files to the updated location. In general, users can upgrade to 0.8 and continue to operate normally. Any applications that customize the storage location or make assumptions about the storage location will need to take this change into consideration. Additionally, after upgrading to 0.8, it is not possible to downgrade to 0.7 without manually moving configuration files. In 1.0, the backward compatibilty will be removed. PR: ports/165606 Submitted by: maintainer, douglas@douglasthrift.net Revision Changes Path 1.11 +1 -1 ports/security/py-keyring/Makefile 1.9 +2 -2 ports/security/py-keyring/distinfo 1.7 +6 -0 ports/security/py-keyring/pkg-plist
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201203021847.q22Ilhup090588>