From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] File collisions
Date: Thu, 19 Apr 2007 11:37:01 +0100 [thread overview]
Message-ID: <f07gul$n3s$2@sea.gmane.org> (raw)
On the issue of QA, I think enabling FEATURES="collision-detect" by default
would do a lot more good at this stage than "test". There are several
packages I have come across where this has picked up files not being
removed from earlier versions. It's a reasonable default to have and
doesn't involve delaying users since it takes a fraction of a second to
carry out. What I'd propose is that portage runs the collision-detect and
reports it, but continues the installation in the same manner as now.
This could tie into an automated report at a later stage.
According to the portage team the majority of blockers in the tree are
`soft' blocks which are file collisions. I understand that they'd like to
separate those from hard blocks which are more fundamental
incompatibilities than installing the same file, since that would make it
easier for QA to track those. collision-detect isn't going to help with
that, of course, but I wonder what the issues would be with such a change?
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2007-04-19 10:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 10:37 Steve Long [this message]
2007-04-19 10:51 ` [gentoo-dev] File collisions 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
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='f07gul$n3s$2@sea.gmane.org' \
--to=slong@rathaus.eclipse.co.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