From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] Improve policy of stabilizations
Date: Sat, 7 Nov 2009 05:00:12 +1300 [thread overview]
Message-ID: <8cd1ed20911060800h4d2f88f8l90efb09c026e1f91@mail.gmail.com> (raw)
In-Reply-To: <8b4c83ad0911060618r2b61c4b4w51238306b9c9a437@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
On Sat, Nov 7, 2009 at 3:18 AM, Nirbheek Chauhan <nirbheek@gentoo.org>wrote:
> On Fri, Nov 6, 2009 at 1:42 AM, Petteri Räty <betelgeuse@gentoo.org>
> wrote:
> > In the past when smaller arches were not that active we used to mark
> > Java packages stable after testing by at least one arch team. The
> > probability to find arch specific issues in something like Java is not
> > so high so I think arrangements like this are acceptable when the arch
> > teams have problems keeping up.
> >
>
> I think the same should be extended to other languages such as Perl
> and Python (unless they have portions which are C/C++)
>
>
You can't really, although Perl has a vm of sorts, the per-arch differences
that occur as a side effect of endianness, different floating point/integer
math ( 32bit vs 64bit ) , and all those differences impact code.
and XS modules of course, they're prone to everything C is prone to.
--
Kent
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, 3 )
for ( 9,8,0,7,1,6,5,4,3,2 );"
http://kent-fredric.fox.geek.nz
[-- Attachment #2: Type: text/html, Size: 1600 bytes --]
next prev parent reply other threads:[~2009-11-06 16:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-01 16:36 [gentoo-dev] [RFC] Improve policy of stabilizations Arfrever Frehtes Taifersar Arahesis
2009-11-01 16:55 ` Mart Raudsepp
2009-11-01 18:19 ` Richard Freeman
2009-11-01 20:21 ` Petteri Räty
2009-11-01 21:16 ` [gentoo-dev] " Ryan Hill
2009-11-02 14:17 ` Christian Faulhammer
2009-11-02 15:23 ` Markos Chandras
2009-11-03 18:10 ` Christian Faulhammer
2009-11-04 12:36 ` Ben de Groot
2009-11-04 12:50 ` Christian Faulhammer
2009-11-04 18:01 ` Tobias Klausmann
2009-11-04 20:49 ` Nirbheek Chauhan
2009-11-04 21:02 ` Joseph Jezak
2009-11-05 3:48 ` Ryan Hill
2009-11-05 9:17 ` Tobias Klausmann
2009-11-05 20:12 ` Petteri Räty
2009-11-06 3:06 ` Joseph Jezak
2009-11-06 14:18 ` Nirbheek Chauhan
2009-11-06 14:45 ` Fabian Groffen
2009-11-06 17:06 ` Nirbheek Chauhan
2009-11-06 17:08 ` Nirbheek Chauhan
2009-11-07 5:13 ` Ryan Hill
2009-11-06 22:07 ` Zac Medico
2009-11-07 3:36 ` Arfrever Frehtes Taifersar Arahesis
2009-11-07 14:54 ` Peter Volkov
2009-11-07 20:49 ` Zac Medico
2009-11-08 0:12 ` Nirbheek Chauhan
2009-11-08 9:31 ` Petteri Räty
2009-11-08 12:55 ` Peter Volkov
2009-11-09 2:34 ` Zac Medico
2009-11-08 9:05 ` Fabian Groffen
2009-11-08 12:53 ` Peter Volkov
2009-11-06 22:52 ` Rémi Cardona
2009-11-07 7:22 ` Hans de Graaff
2009-11-06 16:00 ` Kent Fredric [this message]
2009-11-06 17:00 ` Nirbheek Chauhan
2009-11-07 14:14 ` Tobias Klausmann
2009-11-05 10:52 ` Duncan
2009-11-06 17:18 ` Christian Faulhammer
2009-11-06 17:15 ` Christian Faulhammer
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=8cd1ed20911060800h4d2f88f8l90efb09c026e1f91@mail.gmail.com \
--to=kentfredric@gmail.com \
--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