From: "Bruce A. Locke" <blocke@shivan.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] BitchX and esound
Date: Sun Sep 23 16:44:01 2001 [thread overview]
Message-ID: <20010923184424.2fd3eb55.blocke@shivan.org> (raw)
In-Reply-To: <20010923183241.338f93a8.blocke@shivan.org>
On Sun, 23 Sep 2001 18:32:41 -0400
"Bruce A. Locke" <blocke@shivan.org> wrote:
Ah someone shoot me... I found the source of the problem... Whoever did
the original -r3 BitchX ebuild forgot about the makefile, etc patch we
have in the files directory. I checked in a copy of the patch for -r3
while trying to debug stuff and thats probably why it started building for
other people after I complained. :( With this patch BitchX now detected
esound fine.
Sorry everyone...
> On 23 Sep 2001 17:14:18 +0200
> Mikael Hallendal <micke@codefactory.se> wrote:
>
> > Btw, what idiot would name the package so that 0.2.22 is not newer
than
> > 0.2.5?
>
> I'm assuming this is the case because the test for 0.2.5+ fails in the
> BitchX configure script and the authors website shows 0.2.8 as the most
> recent version. Either way BitchX isn't building for me with 0.2.22.
>
> ---------------------------------------------------------------------
> Bruce A. Locke
> blocke@shivan.org
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
>
---------------------------------------------------------------------
Bruce A. Locke
blocke@shivan.org
next prev parent reply other threads:[~2001-09-23 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-22 21:22 [gentoo-dev] BitchX and esound Bruce A. Locke
2001-09-23 10:09 ` Mikael Hallendal
2001-09-23 10:31 ` Martin Schlemmer
2001-09-23 16:33 ` Bruce A. Locke
2001-09-23 16:44 ` Bruce A. Locke [this message]
2001-09-24 2:50 ` Mikael Hallendal
-- strict thread matches above, loose matches on Subject: below --
2001-09-23 2:15 Martin Schlemmer
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=20010923184424.2fd3eb55.blocke@shivan.org \
--to=blocke@shivan.org \
--cc=gentoo-dev@cvs.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