From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Textrels in packages policy
Date: Wed, 14 Dec 2005 10:25:00 -0500 [thread overview]
Message-ID: <1134573901.3773.26.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <20051214002557.GB1863@toucan.gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1824 bytes --]
On Wed, 2005-12-14 at 00:25 +0000, Mike Frysinger wrote:
> On Tue, Dec 13, 2005 at 05:59:17PM -0600, Jory A. Pratt wrote:
> > Mark Loeser wrote:
> > > Basically what I'm looking for here is an easy to understand explanation of
> > > what textrels are, why they are bad, and why they should hold back marking a
> > > package stable. The only information I've been able to find states that they
> > > could cause a performance hit, but this doesn't seem to warrant banning them
> > > completely in my eyes.
> > >
> > > Getting a clear cut policy on exactly what issues should hold a package back
> > > from being marked stable is what I'm looking for. Issues like textrels,
> > > executable stacks, etc is what I'm looking for to be defined and explained why
> > > we are to always avoid them. This should be added to existing documentation
> > > policy so it is somewhere for new devs to know about, and existing devs to
> > > have for a reference.
> >
> > Only problem I see with this is binary packages. We can not control
> > upstream binaries as everyone is aware of. So when does it become safe
> > to override stable packages that have texrel's and executable stacks?
>
> no idea what you mean by "override", but here's a crazy idea ... ask
> upstream to fix the issues. for example, we just reported executable
> stacks with the ut2004 game and Ryan of epicgames was so kind as to
> fix it up for us. some upstream peeps dont even know about these sort
> of things until you point them out.
Actually, it is not fixed yet. Ryan is aware of the issue, but it was
not fixed in the latest version. There was an error on my part that
made me think it was fixed.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-12-14 15:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 20:59 [gentoo-dev] Textrels in packages policy Mark Loeser
2005-12-13 21:15 ` Mike Frysinger
2005-12-13 22:30 ` Saleem A.
2005-12-14 0:22 ` Mike Frysinger
2005-12-14 1:02 ` Mark Loeser
2005-12-14 1:16 ` Ciaran McCreesh
2005-12-14 1:20 ` Mike Frysinger
2005-12-14 1:37 ` Ciaran McCreesh
2005-12-14 1:43 ` Mike Frysinger
2005-12-14 1:39 ` Mark Loeser
2005-12-14 1:07 ` Ciaran McCreesh
2005-12-14 1:25 ` Mike Frysinger
2005-12-14 1:32 ` Mark Loeser
2005-12-13 23:59 ` Jory A. Pratt
2005-12-14 0:25 ` Mike Frysinger
2005-12-14 2:59 ` Jason Wever
2005-12-14 3:08 ` Mark Loeser
2005-12-14 3:50 ` Mike Frysinger
2005-12-14 6:59 ` Harald van Dijk
2005-12-14 7:51 ` Kevin F. Quinn
2005-12-14 8:19 ` Harald van Dijk
2005-12-14 13:43 ` Mike Frysinger
2005-12-14 14:27 ` Harald van Dijk
2005-12-14 14:38 ` Mike Frysinger
2005-12-14 15:04 ` Harald van Dijk
2005-12-15 7:14 ` Kevin F. Quinn
2005-12-14 15:25 ` Chris Gianelloni [this message]
2005-12-14 15:27 ` Chris Gianelloni
2005-12-14 15:42 ` Mike Frysinger
2005-12-14 7:44 ` Kevin F. Quinn
2005-12-14 9:33 ` Henrik Brix Andersen
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=1134573901.3773.26.camel@cgianelloni.nuvox.net \
--to=wolf31o2@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