From: Todd Berman <tberman@gentoo.org>
To: Georgi Georgiev <chutz-dated-1059395778.939403d6d488@gg3.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] app-cvs
Date: 14 Jul 2003 09:24:36 -0400 [thread overview]
Message-ID: <1058189075.12265.3.camel@phaze> (raw)
In-Reply-To: <20030714123616.GA6884%chutz@gg3.net>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
Just in general, app-cvs is a 'BAD' idea.
It defeats the *entire* purpose of what is going on in general.
However, I fully agree with known good cvs-snapshots being used for
packages in the portage tree, but live cvs ebuilds prevent any sort of
QA in general being done on Gentoo's end. And if you are really wanting
to use cvs, its assumed that you will be updating and recompiling fairly
often, and a live-pull cvs ebuild doesnt really help you.
In general, baring notable exceptions (gaim-cvs, private live-cvs pull
ebuilds) I dont think live-cvs ebuilds are a good idea at all, and
surely not a sound reason to add a category just for their use.
Sorry if this is a bit rambling, just woke up :)
--Todd
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-14 13:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 9:25 [gentoo-dev] app-cvs Tal Peer
2003-07-14 9:26 ` FRLinux
2003-07-14 9:40 ` Michele Balistreri
2003-07-14 10:24 ` Svyatogor
2003-07-14 10:42 ` rob holland
2003-07-14 11:12 ` Luca Barbato
2003-07-14 11:49 ` Michele Balistreri
2003-07-14 11:41 ` Dhruba Bandopadhyay
2003-07-14 11:18 ` Patrick Kursawe
2003-07-14 12:36 ` Georgi Georgiev
2003-07-14 13:24 ` Todd Berman [this message]
2003-07-14 17:55 ` Paul de Vrieze
2003-07-15 15:13 ` [gentoo-dev] Categorization [was: app-cvs] Markus Bertheau
2003-07-15 18:56 ` [gentoo-dev] app-cvs Dan Armak
2003-07-15 7:23 ` Alvaro Figueroa Cabezas
2003-07-17 13:31 ` Michael Andrews
2003-07-19 2:41 ` James H. Cloos Jr.
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=1058189075.12265.3.camel@phaze \
--to=tberman@gentoo.org \
--cc=chutz-dated-1059395778.939403d6d488@gg3.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