From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] app-accessibility/speech-tools-1.2.96_beta build fails
Date: Tue, 30 Jun 2009 20:45:54 +0200 [thread overview]
Message-ID: <200906302045.54519.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <20090630105410.2ca19943@lappy.evolone.org>
On Tuesday 30 June 2009 19:54:10 Michael Higgins wrote:
> Detected file collision(s):
>
> /usr/bin/dp
>
> Searching all installed packages for file collisions...
>
> Press Ctrl-C to Stop
>
> mail-client/nmh-1.1-r1
> /usr/bin/dp
>
> Package 'app-accessibility/speech-tools-1.2.96_beta' NOT merged due to
> file collisions. If necessary, refer to your elog messages for the
> whole content of the above message.
Did you do this step?
Did it tell you anything useful?
> So, it seems both packages install the same file. WTF? Am I dead in the
> water now?
Not necessarily. Usually one would persuade one of the ebuilds to not build
the offending file by removing some USE flag. That doesn't apply to those
packages (no relevant USE flags) so your options are:
a. figure out which of the packages you can do without, and do so. (Do you
REALLY need a speech synthesizer?)
b. Examine each package's output of ./configure and see if there's a way to
disable something that will avoid collisions. Then build that package
manually.
c. Do b) but modify the ebuild and store it in your local overlay
d. Put on your cowboy hat (the black one), delete /usr/bin/dp and let rip with
emerge. This is an option, just not a recommended one.
Either way, you should file a bug and provide any workable solutions you
found.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-06-30 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 17:54 [gentoo-user] app-accessibility/speech-tools-1.2.96_beta build fails Michael Higgins
2009-06-30 18:45 ` Alan McKinnon [this message]
2009-06-30 19:04 ` Willie Wong
2009-06-30 19:26 ` Alan McKinnon
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=200906302045.54519.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--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