public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Shaw <ryan.shaw@stanfordalumni.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Question about portage
Date: 06 Jun 2002 23:04:00 +0900	[thread overview]
Message-ID: <1023372266.3752.10.camel@momo> (raw)
In-Reply-To: <80C9B7B2-794A-11D6-9957-0003930A8D14@cty-net.ne.jp>

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

On Thu, 2002-06-06 at 21:39, Takamoto Ando wrote:

> Hello!
> My name is Takamoto from Japan.
> i just start gentoo today.

ようこそ。:^)

> I want to make some portage for Japanese.

Do you mean you want to create some ebuilds for Japanese 
software, or you want to localize portage itself?

> Also I want to patch to kde's .ebuild file(Bugfix for Japanese)
> 
> usually I patch as below
> download patchfile (ex.koffice-2.0.1-kpresenter-xim-20001207.diff)
> then
> bzip2 -dc koffice-2.0.tar.bz2 | tar xvf -
> patch -p0 < koffice-2.0.1-kpresenter-xim-20001207.diff
> 
> Can I include this routine to .ebuild file??

This patch is from December 2000 and it still works?
Why hasn't it been accepted into the main KDE tree yet?

BTW, here are links to some ebuilds that haven't been
accepted into the official portage tree yet which you
may be interested in:

kinput2 (canna is already in the main tree): 
http://bugs.gentoo.org/show_bug.cgi?id=2819

kochi japanese trutype fonts: 
http://bugs.gentoo.org/show_bug.cgi?id=2885

libtrain/gtktrain (like ekispato):
http://bugs.gentoo.org/show_bug.cgi?id=3446
http://bugs.gentoo.org/show_bug.cgi?id=3447

ryan



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-06-06 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06 12:39 [gentoo-dev] Question about portage Takamoto Ando
2002-06-06 14:04 ` Ryan Shaw [this message]
2002-06-06 15:27 ` Bart Verwilst
  -- strict thread matches above, loose matches on Subject: below --
2002-06-06 15:21 Sean P. Kane

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=1023372266.3752.10.camel@momo \
    --to=ryan.shaw@stanfordalumni.org \
    --cc=gentoo-dev@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