From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: HLDS discussion
Date: Wed, 6 Aug 2003 19:09:17 -0400 [thread overview]
Message-ID: <200308061909.18250.vapier@gentoo.org> (raw)
In-Reply-To: <200308061050.07606.stuart@gentoo.org>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 2209 bytes --]
On Wednesday 06 August 2003 05:50, Stuart Herbert wrote:
> On Wednesday 06 August 2003 4:38 am, Mike Frysinger wrote:
> > i maintain them ... and if you look at the date on the d ebuild you'll
> > find it was in portage a few hours after d was released ;)
>
> d's an experimental patch. Why is it the only version in portage?
ive been outta the hlds loop for almost a year now ... hopefully ill be able
to get my ns server up again in a few weeks :)
i only ever had the 3.1.1.1 ebuilds in portage because i saw they fixed
exploits ...
> > as for adding back in older versions, ill look into it ...
>
> Seems a shame to have an ebuild only for a version that is well-known as
> broken ...
yep, 3.1.1.0, 3.1.1.1, and 3.1.1.1d are now in portage
> Especially as your ebuild for NS-2 installs the 3.1.1.0c version of NS, and
> (unless I've missed it in the ebuild) doesn't include the patch to make
> NS-2 run on 3.1.1.1d.
URL for said patch ? :)
> > i'm still trying to make hlds work properly on 1.0/1.2/1.4 boxes ...
> > glibc seems to cause issues of course :/
>
> libs-compat fixes that for me just fine, at least with 3.1.1.0c + boffix.
URL for boffix ? ;)
and did you mean 3.1.1.0 ? or 3.1.1.1c ?
> I also noticed that Metamod is built from source. HLDS (which is a C++
> program) is very sensitive to which version of GCC is used to build Metamod
> (and Metamods), and most people find it seg faults most of the time when
> compiled from source. It might be worth adding an ebuild for the binary
> release of Metamod - or talk to Will Day (metamod's author) to discuss
> which GCC & CXXFLAGS are likely to bring the most success.
yeah, i added 1.16.2 today which defaults to binary install unless user has
USE=src ... oddly it worked for me just fine ... or i could just be smokin
crack ...
> I'd also be very interested in seeing HLDS support the +vhosts scheme we've
> been discussing about webapps.
i havent been following webapps so i have no idea what you're refering to ...
but my first thought is 'what the hell does webapps/vhosts have to do with
hlds ?' ... only relation that pops into my head is hlstat support ...
-mike
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2003-08-06 23:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 23:45 [gentoo-dev] Beta ebuild for game called 'Nevermind' Stuart Herbert
2003-08-05 23:51 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2003-08-06 1:04 ` [gentoo-dev] " Chris Gianelloni
2003-08-06 2:00 ` Stuart Herbert
2003-08-06 2:24 ` Chris Gianelloni
2003-08-06 2:48 ` Stuart Herbert
2003-08-06 2:33 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2003-08-06 3:38 ` [gentoo-dev] " Mike Frysinger
2003-08-06 9:50 ` [gentoo-dev] HLDS discussion Stuart Herbert
2003-08-06 23:09 ` Mike Frysinger [this message]
2003-08-06 1:10 ` [gentoo-dev] Beta ebuild for game called 'Nevermind' Chris Gianelloni
2003-08-06 2:08 ` Stuart Herbert
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=200308061909.18250.vapier@gentoo.org \
--to=vapier@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