From: Meir Kriheli <mksoft@netvision.net.il>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] dev-db/firebird-1.0.3 - Please test
Date: Mon, 16 Jun 2003 01:26:40 +0300 [thread overview]
Message-ID: <200306160126.40805.mksoft@netvision.net.il> (raw)
Hello,
Please help testing the new ebuild for dev/db-firebird. It's currently marked
as ~x86, so make sure to have it in ACCEPT_KEYWORDS.
This ebuild should close bugs #15071 and #16237. It features the following
changes:
- Kills lingering gds_lock_mgr processes left after emerging (#15071)
- latest stable firebird release - 1.0.3.972 (#16237)
- firebird placed under /etc/xinet.d (disabled by default)
- 70firebird placed under env.d to add PATH, ROOT_PATH and CONFIG_PROTECT
- config function to add gds_db to /etc/services
- isc4.gdb and isc_config moved to /etc/firebird and symlinks to them under
/opt/interbase added. This will prevent fututre emerges from overwriting the
passwords db (which is the current situation).
Right now it is just for the classic (i.e: inet) server. The super (i.e.:
standalone daemon) will be added hopefully soon.
Please backup your current isc4.gdb if you have any and move it to
/opt/firebird after emerge.
Cheers
--
Meir Kriheli
MKsoft systems
--
gentoo-dev@gentoo.org mailing list
reply other threads:[~2003-06-15 22:25 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=200306160126.40805.mksoft@netvision.net.il \
--to=mksoft@netvision.net.il \
--cc=gentoo-dev@gentoo.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