From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: debian etch sh3 and sh4
Date: Tue, 22 Jan 2008 00:37:21 +0000 [thread overview]
Message-ID: <20080122003721.GA26756@linux-sh.org> (raw)
In-Reply-To: <82C85C285793D5ebiharaml@si-linux.com>
On Mon, Jan 21, 2008 at 09:22:51PM +0900, Yutaro Ebihara wrote:
> please let me introduce my archives.
> this is debian etch sh3 and sh4
> http://www.si-linux.co.jp/pub/debian-sh/
>
> base tar balls.
> http://www.si-linux.co.jp/pub/debian-sh/base/etch/
>
> you can use following apt line in your sh-box.
>
> landy2:~# cat /etc/apt/sources.list
> deb http://www.si-linux.co.jp/pub/debian-sh etch main contrib non-free
> deb-src http://ftp.debian.org/debian/ etch main contrib non-free
>
These sorts of efforts seem to pop up almost every other year, and then
quickly fall in to disarray. The same can be said for the Fedora Core
ports. Is there a plan to have this work merged back in to Debian proper,
and to keep it updated?
Currently Gentoo is the only viable option for a reasonably maintained
port, and the only one supported upstream. Seeing Debian or Fedora Core
in the same state would be nice, but the porters need to get serious
about what their goals are. A one-shot build is obsolete before it hits
the mailing list.
next prev parent reply other threads:[~2008-01-22 0:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 12:22 debian etch sh3 and sh4 Yutaro Ebihara
2008-01-22 0:37 ` Paul Mundt [this message]
2008-01-22 11:54 ` Adrian McMenamin
2008-01-22 12:32 ` Paul Mundt
2008-01-22 14:34 ` Mike Frysinger
2008-01-22 15:04 ` Adrian McMenamin
2008-01-22 22:49 ` Mike Frysinger
2008-01-23 9:29 ` Adrian McMenamin
2008-01-23 9:40 ` Manuel Lauss
2008-01-23 9:53 ` Paul Mundt
2008-01-23 10:28 ` Adrian McMenamin
2008-01-23 12:16 ` Mike Frysinger
2008-01-23 13:30 ` Kristoffer Ericson
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=20080122003721.GA26756@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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