public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re: Emerging package as both 64 and 32 bit
Date: Mon, 18 Dec 2006 09:31:31 +0000	[thread overview]
Message-ID: <20061218093131.73994121@krikkit.digimed.co.uk> (raw)
In-Reply-To: <em1llc$c1j$2@sea.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 444 bytes --]

On Sat, 16 Dec 2006 20:41:16 +0000 (UTC), Duncan wrote:

> there's little reason to do 32-bit at all, here, except to keep
> from having to use the grub binary package.

What's wrong with the GRUB source package? I remember using grub-static
when I first went 64 bit, but haven't used it for ages. The only 32 bit
stuff I use here is firefox-bin and vmware.


-- 
Neil Bothwick

I just took an IQ test. The results were negative.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-12-18  9:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-16 15:45 [gentoo-amd64] Emerging package as both 64 and 32 bit Boky Boky
2006-12-16 17:09 ` Indarios
2006-12-16 18:15 ` Mike Doty
2006-12-16 18:17 ` [gentoo-amd64] " Duncan
2006-12-16 19:24   ` Boky
2006-12-16 20:08   ` Kevin F. Quinn
2006-12-16 20:41     ` Duncan
2006-12-18  9:31       ` Neil Bothwick [this message]
2006-12-18 10:22         ` Simon Stelling
2006-12-18 10:34           ` Neil Bothwick
2006-12-18 12:39           ` Duncan
2006-12-18 14:10             ` Etaoin Shrdlu
2006-12-19 15:01               ` Duncan
2006-12-20 21:49                 ` Etaoin Shrdlu
2006-12-21  9:31                   ` Duncan
2006-12-22  7:02             ` Mike Doty
2006-12-22 14:54               ` Boyd Stephen Smith Jr.
2006-12-22 21:20                 ` Duncan
2006-12-23  3:44                   ` Boyd Stephen Smith Jr.

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=20061218093131.73994121@krikkit.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-amd64@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