From: Jeremy Maitin-Shepard <jbms@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] portage-ng i18n?
Date: Wed, 07 Jan 2004 22:31:19 -0500 [thread overview]
Message-ID: <87oetfqfp4.fsf@jbms.ath.cx> (raw)
In-Reply-To: <20031230081356.GB12956@unm.edu> (Jason Mobarak's message of "Tue, 30 Dec 2003 01:13:56 -0700")
Jason Mobarak <aether@gentoo.org> writes:
> The current portage spec lists a component based design as goal for portage,
> constructing an i18n emerge-like tool would present less difficulty if
> portage-ng has a good component design.
There might be advantages to a `component-based design' (obviously that
phrase is subject to diverse interpretation), but I do not see how ease
of internationalization is one such particular advantage.
--
Jeremy Maitin-Shepard
--
gentoo-portage-dev@gentoo.org mailing list
prev parent reply other threads:[~2004-01-08 3:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200312241917.43532.spatz@012.net.il>
[not found] ` <8457DCDA-365D-11D8-93E7-0003938E7E46@gentoo.org>
[not found] ` <200312261814.49960.spatz@psybear.com>
2003-12-30 8:13 ` [gentoo-portage-dev] portage-ng i18n? Jason Mobarak
2004-01-07 15:01 ` foser
2004-01-07 16:01 ` Jason Stubbs
2004-01-08 0:00 ` foser
2004-01-08 1:57 ` Jason Stubbs
2004-01-08 3:17 ` Jeremy Maitin-Shepard
2004-01-08 10:01 ` Paul de Vrieze
2004-01-08 22:25 ` Jeremy Maitin-Shepard
2004-01-08 3:31 ` Jeremy Maitin-Shepard [this message]
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=87oetfqfp4.fsf@jbms.ath.cx \
--to=jbms@gentoo.org \
--cc=gentoo-portage-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