public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [ANNOUNCE]: IA64 ISOs based on Fedora Core 5
Date: Wed, 05 Apr 2006 11:24:15 +0000	[thread overview]
Message-ID: <1144236255.6227.30.camel@pmac.infradead.org> (raw)
In-Reply-To: <44332325.8050207@sgi.com>

On Wed, 2006-04-05 at 06:54 -0400, Prarit Bhargava wrote:
> > To be honest, I'm not convinced that weekly ISO builds are particularly
> > useful -- we don't do that for rawhide on other architectures either.
> > It's probably better just to encourage people to use rsync to keep up
> > with rawhide, rather than downloading it all over again each week.
> 
> Unfortunately, it seems I have users who are unwilling to use yum, etc., 
> in the short term.  They would prefer weekly snapshots.

They actually want to _reinstall_ weekly? Or do a full 'upgrade' weekly?

Even so, they could quite happily do that from a normal rawhide mirror
like everyone else does, rather than using ISO images. That just seems
like a gratuitous waste of bandwidth to me -- for rawhide even more so
than for the actual releases.

> Yep -- I replaced fedora-release with the FC5 version in the images.  I 
> didn't mention it because I didn't think it was that important :).

The _real_ FC5 version -- doesn't that mean the updates repo is
configured to point at a non-existent directory? 

> > Aside from the updates, the next task is building Extras and Livna for
> > IA64, of course...
> 
> Whaddya think I'm working on? :)

:)


-- 
dwmw2


  parent reply	other threads:[~2006-04-05 11:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05  1:53 [ANNOUNCE]: IA64 ISOs based on Fedora Core 5 Prarit Bhargava
2006-04-05  2:25 ` Paul Nasrat
2006-04-05  9:44 ` David Woodhouse
2006-04-05 10:52 ` Prarit Bhargava
2006-04-05 10:54 ` Prarit Bhargava
2006-04-05 11:24 ` David Woodhouse [this message]
2006-04-05 12:08 ` Paul Nasrat
2006-04-05 12:16 ` Paul Nasrat

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=1144236255.6227.30.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=linux-ia64@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