From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Chris Bainbridge <c.j.bainbridge@ed.ac.uk>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Stuff that makes people mad
Date: Fri, 21 May 2004 14:35:49 -0400 [thread overview]
Message-ID: <1085164549.25140.82.camel@localhost> (raw)
In-Reply-To: <200405211742.44615.c.j.bainbridge@ed.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
On Fri, 2004-05-21 at 12:42, Chris Bainbridge wrote:
> Ebuilds are trapped in their own directory, I don't see how adding them messes
> up other ebuilds. Unless you mean that they can do bad things like
> overwriting libc, which would be pretty obvious and reported straight away by
> users of the ebuild.
Don't you see, this is *exactly* what we want to avoid. Why should we
have to take the time to try and fix a rogue ebuild that was
*automatically* added to the tree? Especially considering the amount of
time that can be wasted in fixing something like a broken libc.
--
Chris Gianelloni
Developer
Games/LiveCD Teams
Gentoo Linux
Is your power animal a penguin?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-21 18:27 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 1:46 [gentoo-dev] Stuff that makes people mad C. Brewer
2004-05-21 4:08 ` Andrew Gaffney
2004-05-21 6:33 ` Robin H. Johnson
2004-05-21 13:19 ` John Nilsson
2004-05-21 13:39 ` Chris Gianelloni
2004-05-21 14:54 ` Chris Bainbridge
2004-05-21 15:04 ` Stephen Becker
2004-05-21 16:29 ` Josh Glover
2004-05-21 16:36 ` Jon Portnoy
2004-05-21 16:40 ` Ciaran McCreesh
2004-05-21 17:39 ` Josh Glover
2004-05-21 17:59 ` Ciaran McCreesh
2004-05-21 22:07 ` Mike Frysinger
2004-05-23 15:54 ` Karl Trygve Kalleberg
2004-05-23 17:13 ` Joseph Booker
2004-05-23 21:46 ` Karl Trygve Kalleberg
2004-05-21 18:14 ` Christian Gut
2004-05-21 18:36 ` Marius Mauch
2004-05-21 20:53 ` Joseph Booker
2004-05-21 18:55 ` Chris Gianelloni
2004-05-21 15:32 ` Jason Stubbs
2004-05-21 16:12 ` Chris Bainbridge
2004-05-21 16:33 ` Ciaran McCreesh
2004-05-21 16:42 ` Chris Bainbridge
2004-05-21 16:53 ` Ciaran McCreesh
2004-05-21 18:35 ` Chris Gianelloni [this message]
2004-05-21 17:40 ` Jason Stubbs
2004-05-21 15:39 ` Chris Gianelloni
2004-05-21 15:42 ` Jason Stubbs
2004-05-25 16:02 ` Jean Jordaan
2004-05-21 15:43 ` Tom Payne
2004-05-21 16:11 ` Allen Dale Parker
2004-05-21 16:19 ` Jon Portnoy
2004-05-21 19:49 ` Stuart Herbert
2004-05-21 16:59 ` John Nilsson
2004-05-21 17:14 ` Jon Portnoy
2004-05-21 17:16 ` Tom Payne
2004-05-21 17:25 ` Jason Stubbs
2004-05-21 21:59 ` John Nilsson
2004-05-21 22:06 ` Stuart Herbert
2004-05-21 22:34 ` John Nilsson
2004-05-21 22:43 ` Joseph Booker
2004-05-23 13:42 ` John Nilsson
2004-05-21 18:45 ` Chris Gianelloni
2004-05-21 22:28 ` John Nilsson
2004-05-21 22:40 ` Joseph Booker
2004-05-21 23:27 ` John Nilsson
2004-05-21 23:59 ` Joseph Booker
2004-05-22 3:29 ` John Nilsson
2004-05-22 13:02 ` Stuart Herbert
2004-05-23 14:05 ` John Nilsson
2004-05-23 14:45 ` Allen Dale Parker
2004-05-23 19:56 ` John Nilsson
2004-05-23 15:40 ` Joseph Booker
2004-05-23 21:17 ` John Nilsson
2004-05-23 23:12 ` Marius Mauch
2004-05-24 1:26 ` John Nilsson
2004-05-23 23:34 ` Joseph Booker
2004-05-24 4:11 ` [gentoo-dev] " Duncan
2004-05-24 4:59 ` John Nilsson
2004-05-24 8:21 ` Paul de Vrieze
2004-05-21 18:42 ` [gentoo-dev] " Stuart Herbert
2004-05-21 13:30 ` 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=1085164549.25140.82.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=c.j.bainbridge@ed.ac.uk \
--cc=gentoo-dev@lists.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