public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matthias Hanft <mh@hanft.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] How to handle Firebird with PHP now
Date: Mon, 10 Feb 2025 20:07:07 +0100	[thread overview]
Message-ID: <27416a10-0532-32df-df43-7e51841c29bf@hanft.de> (raw)

Hi,

I have many Firebird databases on my Gentoo server.

To compile PHP with Firebird support, I have the line

-firebird

in /etc/portage/profile/use.mask because the Firebird USE flag
of PHP was masked somewhen.

This worked without problems as long as Firebird (3.0) was in
the portage tree.

Now Firebird was completely removed from the portage tree.
So I installed Firebird (5.0) from its own homepage which
works without problems, too. I put the line

dev-db/firebird-5.0.1.1469

into /etc/portage/profile/package.provided. Not sure if this
was necessary, but apparently it doesn't harm...

...maybe except one point: Since then, revdep-rebuild always
reinstalls PHP (although it doesn't show any orphaned files).

The other/old revdep-rebuild.sh says, however,
"Dynamic linking on your system is consistent... All done."

I'd like to get the normal revdep-rebuild saying "everything
ok", too. So what's the correct way to deal with a manually
installed Firebird server while keeping the Firebird support
in PHP and not interfering with revdep-rebuild?

Thanks,

-Matt


             reply	other threads:[~2025-02-10 19:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 19:07 Matthias Hanft [this message]
2025-02-10 20:11 ` [gentoo-user] How to handle Firebird with PHP now Michael
2025-02-11  9:09   ` Matthias Hanft
2025-02-11 10:02     ` Michael
2025-02-11 16:30       ` Matthias Hanft
2025-02-11 18:12         ` Michael Orlitzky
2025-02-14 12:47           ` Matthias Hanft
2025-02-15  3:11             ` Michael Orlitzky
2025-02-14 13:29   ` Viorel Munteanu

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=27416a10-0532-32df-df43-7e51841c29bf@hanft.de \
    --to=mh@hanft.de \
    --cc=gentoo-user@lists.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