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 12:32:27 +0000 [thread overview]
Message-ID: <20080122123227.GA8587@linux-sh.org> (raw)
In-Reply-To: <82C85C285793D5ebiharaml@si-linux.com>
On Tue, Jan 22, 2008 at 11:54:16AM -0000, Adrian McMenamin wrote:
> On Tue, January 22, 2008 12:37 am, Paul Mundt wrote:
> > 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.
>
> Whilst I obviously accept a lot of what Paul says is true, I wanted to
> record my appreciation of the effort and let you know that the core at
> least runs on the Dreamcast (though I need to fix it up properly to get
> the filesystem to work).
>
> If this was going to be a supported project in the longer term I'd be
> willing to consider providing space and bandwidth for a European mirror.
>
The problem is that this is still just a stop-gap solution. Debian
already has all of the mirror infrastructure in place, so the only thing
that needs to happen is effort to get this work integrated. If that's not
going to happen, this simply isn't going to go anywhere. We've seen this
with both the Debian and the Fedora Core ports in the past, and there's
no reason to imagine things will be any different this time. It's nice to
see that people are putting effort in to this, but without a push to get
it supported upstream, it will simply bitrot like all of the other ports.
This is the reality of things, good intentions aside.
> On gentoo - the link on the wiki points to sources that are 18 months
> old... is there something more up to date?
It points to stage tarballs that are still usable. You of course need
to update once you have it set up on your platform, but the stage
tarballs are a starting point only. There are updates every day, and this
continues to be the only maintained port.
next prev parent reply other threads:[~2008-01-22 12:32 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
2008-01-22 11:54 ` Adrian McMenamin
2008-01-22 12:32 ` Paul Mundt [this message]
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=20080122123227.GA8587@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