From: Chris Gianelloni <wolf31o2@gentoo.org>
To: brettholcomb@charter.net
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Winex-cvs being removed from portage?
Date: 24 Jul 2003 22:01:37 -0400 [thread overview]
Message-ID: <1059098497.23507.6.camel@vertigo> (raw)
In-Reply-To: <auto-000102501131@remt23.cluster1.charter.net>
Here's a basic summary from the way I see it from watching the
discussion.
On Thu, 2003-07-24 at 21:42, Brett I. Holcomb wrote:
> Good point. Could we know the reason it's being considered? If it's license
> philosophy. If there are other reasons can we know them and maybe comment on
> them, too?
How about because they asked us to? Essentially, we have been asked to
not create an automated process to allow a user to install winex from
cvs. The anonymous cvs is there for people to assist in development
with winex. Technically, there is nothing stopping us from continuing
to provide winex-cvs ebuilds. However, Gentoo is part of a larger
community and quite simply, you don't maintain your status as a useful
member of the community if you go around pissing off your neighbors. In
fact, there is nothing keeping Transgaming from pulling the anonymous
cvs access for the winex sources from sourceforge and making it
available to subscriber's only.
> many apps (not just games) that's an important consideration. Yes, we could
> get it from Transgaming but then I have to install a non-ebuild app on my
> system and I lose the advantages of portage.
Copy your winex tarballs to /usr/portage/distfiles and emerge
winex-transgaming. The ebuild which installs the binary version of
winex isn't going anywhere.
--
Chris Gianelloni
Developer, Gentoo Linux
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-25 2:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 5:08 [gentoo-dev] Winex-cvs being removed from portage? dean .
2003-07-23 5:42 ` Seemant Kulleen
2003-07-25 1:01 ` Andrew Cowie
2003-07-25 1:42 ` Brett I. Holcomb
2003-07-25 1:45 ` Nick Hadaway
2003-07-25 2:01 ` Chris Gianelloni [this message]
2003-07-25 3:47 ` Owen Gunden
2003-07-25 4:14 ` Mike Frysinger
2003-07-25 4:35 ` Luke-Jr
2003-07-25 14:31 ` Adrian Almenar
2003-07-26 0:20 ` Luke-Jr
2003-07-26 13:34 ` Chris Gianelloni
2003-07-25 6:13 ` Paul de Vrieze
2003-07-25 9:49 ` Patrick Lauer
2003-07-25 10:00 ` Patrick Kursawe
2003-07-25 11:54 ` Chris Gianelloni
2003-07-25 12:26 ` Patrick Lauer
2003-07-25 13:17 ` Chris Gianelloni
2003-07-25 14:06 ` Dan Armak
2003-07-25 10:53 ` Svyatogor
2003-07-25 11:38 ` Chris Gianelloni
2003-07-25 14:08 ` Thomas de Grenier de Latour
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=1059098497.23507.6.camel@vertigo \
--to=wolf31o2@gentoo.org \
--cc=brettholcomb@charter.net \
--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