From: "Olivier Crête" <tester@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] imlate x86 Editon and more x86 fun
Date: Thu, 11 Aug 2005 23:15:17 -0400 [thread overview]
Message-ID: <1123816517.8746.18.camel@TesterBox.tester.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
Hi,
After Ciaran's comment on -core, I wondered how imlate would fare on
x86. For those who are not familiar with it, imlate list all packages on
one architecture that are outdated compared to another architecture. All
other architectures use x86 as a reference.. That clearly didn't work
for us. So I hacked it to compare x86 to all other Linux keywords.
The results are surprising, 214 packages are more recent on non-x86
architectures. But its pretty hard to know if its because they have arch
specific patches or because the maintainer's arch is not x86... We
should really have a way to specify in the ebuild or metadata.xml what
arch is the maintainer arch.
I also ran the notx86 (notamd64 renamed) script on the tree (it finds
packages that dont have an x86 keyword at all)... and I handfiltered the
result for obvious errors..
This is all available at http://dev.gentoo.org/~tester/imlate/
Ah yea, and I also tried my new imlate script on amd64 and it finds
about 50% more packages than the regular version..
We really need to form an x86 team...
--
Olivier Crête
tester@gentoo.org
x86 Security Liaison
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-08-12 3:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 3:15 Olivier Crête [this message]
2005-08-12 4:53 ` [gentoo-dev] imlate x86 Editon and more x86 fun Chris White
2005-08-12 18:39 ` Olivier Crete
2005-08-12 5:39 ` Robin H. Johnson
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=1123816517.8746.18.camel@TesterBox.tester.ca \
--to=tester@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