From: Stroller <root@stellar.eclipse.co.uk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Enemy Territory ebuild
Date: Sat, 18 Oct 2003 20:39:38 +0100 [thread overview]
Message-ID: <CF67080A-01A2-11D8-A06D-000A95795F3E@stellar.eclipse.co.uk> (raw)
In-Reply-To: <1066483836.28203.13.camel@localhost>
On Oct 18, 2003, at 2:30 pm, Chris Gianelloni wrote:
> I want to ask the opinion of everyone.....
>
> Well, I am thinking of breaking up the enemy-territory ebuilds into two
> ebuilds. There would be an enemy-territory ebuild, which would use the
> original download + patches (and therefore be dial-up friendly) and the
> enemy-territory-full ebuild, which would always download and install
> the
> complete game from the most recent version. This should satisfy both
> camps...
Why not have a new USE flag, called "patches", which says to patch the
original source if possible..?
After all, one can never have enough USE flags. ;-P
Stroller.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-10-18 19:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 13:30 [gentoo-dev] Enemy Territory ebuild Chris Gianelloni
2003-10-18 18:13 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2003-10-18 19:27 ` [gentoo-dev] " Matt Thrailkill
2003-10-18 21:53 ` Mike Frysinger
2003-10-19 0:08 ` Luke-Jr
2003-10-20 7:48 ` Matt Thrailkill
2003-10-18 19:39 ` Stroller [this message]
2003-10-19 13:31 ` Corvus Corax
2003-10-19 14:01 ` Chris Gianelloni
2003-10-20 6:06 ` Mike Frysinger
[not found] ` <B6AD5486-01A2-11D8-A06D-000A95795F3E@stellar.eclipse.co.uk>
2003-10-19 13:52 ` Chris Gianelloni
2003-10-21 12:39 ` Dhruba Bandopadhyay
2003-10-21 13:15 ` Chris Gianelloni
[not found] ` <893C9795-03ED-11D8-AF70-000A95795F3E@stellar.eclipse.co.uk>
2003-10-21 20:23 ` [gentoo-dev] Re: Use of USE flags..? Was: " Chris Gianelloni
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=CF67080A-01A2-11D8-A06D-000A95795F3E@stellar.eclipse.co.uk \
--to=root@stellar.eclipse.co.uk \
--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