From: Christian Faulhammer <opfer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: File collisions
Date: Fri, 20 Apr 2007 11:05:46 +0200 [thread overview]
Message-ID: <20070420110546.76677c05@luna.home> (raw)
In-Reply-To: <f63a4d630704200006j716eeccalc4058edb0218d77f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
"Rob C" <hyakuhei@gentoo.org>:
> On 19/04/07, Christian Faulhammer <opfer@gentoo.org> wrote:
> > Steve Long <slong@rathaus.eclipse.co.uk>:
> > > On the issue of QA, I think enabling FEATURES="collision-detect"
> > > by default would do a lot more good at this stage than "test".
> > Arch teams normally have collision-protect enabled when doing
> > keywording/stabling....in my eyes this is sufficient.
> Its obviously not, Many users are reporting file-collisions on a
> weekly basis. So either this isn't sufficient or the arch teams are
> not acting as you describe.
I can only speak for x86 team where it is mandatory for arch testers
and devs. As far as I can tell other architecture teams handle it the
same. Jakub already pointed out that many have very minimal chroots
for stabling, while my chroot is cluttered with 1500 packages which
should detect a lot of collisions.
Just out of interest: How many file-collisions are filed per-week?
V-Li
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-20 9:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 10:37 [gentoo-dev] File collisions Steve Long
2007-04-19 10:51 ` Ioannis Aslanidis
2007-04-19 11:05 ` [gentoo-dev] " Steve Long
2007-04-19 12:04 ` Christian Faulhammer
2007-04-20 7:06 ` Rob C
2007-04-20 7:21 ` Jakub Moc
2007-04-20 9:21 ` Christian Faulhammer
2007-04-20 7:34 ` Alin Năstac
2007-04-20 9:05 ` Christian Faulhammer [this message]
2007-04-20 11:16 ` Chris Gianelloni
2007-04-20 16:03 ` Joshua Jackson
2007-04-20 16:25 ` Rob C
2007-04-20 17:01 ` Steve Dibb
2007-04-20 17:17 ` Matthias Langer
2007-04-20 17:56 ` Marijn Schouten (hkBst)
2007-04-20 19:12 ` Matthias Langer
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=20070420110546.76677c05@luna.home \
--to=opfer@gentoo.org \
--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