From: Robin H.Johnson <robbat2@gentoo.org>
To: Brad Laue <brad@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] virtual/imap brain damage?
Date: Tue, 22 Jul 2003 15:30:07 -0700 [thread overview]
Message-ID: <20030722223007.GB23878@cherenkov.orbis-terrarum.net> (raw)
In-Reply-To: <3F1D7A4F.8040801@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
On Tue, Jul 22, 2003 at 01:54:23PM -0400, Brad Laue wrote:
> While running emerge -up world on a server of mine I noticed a conflict
> between imap-uw and the c-client ebuilds, both of which, I reasoned,
> would be satisfied with a virtual/imap virtual.
> Point 2 Is important, it solves a blocker issue with mod_php at the moment.
The blocker showed up because virtual/imap-c-client was implemented
and old installs of uw-imap did not provide that virtual. If you _want_
to use uw-imap, just re-emerge it from source and all will be good. If
you don't want it (eg you just want IMAP support in mod_php), then
unmerge uw-imap.
> I browsed through /etc/make.profile/virtuals to make sure there wasn't
> one, and found this:
>
> virtual/imapUW net-mail/uw-imap
> virtual/imapd net-mail/courier-imap
> virtual/imap-c-client net-libs/c-client
>
> Suggestions:
>
> 1) uw-imap and courier-imap can go under virtual/imapd
These are several other imap servers already provide virtual/imapd.
> 2) c-client and uw-imap can go under virtual/imap-c-client.
c-client, uw-imap and vimap ALREADY provide virtual/imap-c-client
--
Robin Hugh Johnson
E-Mail : robbat2@orbis-terrarum.net
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ# : 30269588 or 41961639
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2003-07-22 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 17:54 [gentoo-dev] virtual/imap brain damage? Brad Laue
2003-07-22 18:36 ` Marius Mauch
2003-07-22 22:30 ` Robin H.Johnson [this message]
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=20030722223007.GB23878@cherenkov.orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=brad@gentoo.org \
--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