From: Prarit Bhargava <prarit@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [ANNOUNCE]: IA64 ISOs based on Fedora Core 5
Date: Wed, 05 Apr 2006 10:54:26 +0000 [thread overview]
Message-ID: <4433A1E2.5060308@sgi.com> (raw)
In-Reply-To: <44332325.8050207@sgi.com>
David Woodhouse wrote:
> On Tue, 2006-04-04 at 22:25 -0400, Paul Nasrat wrote:
>
>>I assume for the weekly snapshots of rawhide that you'll be putting
>>unique (eg date based) names on the isos so they can be readily
>>identified, else you're going to run into trouble tracking issues
>>across media sets.
>
>
> 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.
>
>> Do these isos correspond with FC5 or a random snapshot?
>
>
> Rawhide for about a week leading up to March 20th was identical to FC5
> in all but the 'fedora-release' package.
>
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 :).
> Aside from the updates, the next task is building Extras and Livna for
> IA64, of course...
>
Whaddya think I'm working on? :)
P.
next prev parent reply other threads:[~2006-04-05 10:54 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 [this message]
2006-04-05 11:24 ` David Woodhouse
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=4433A1E2.5060308@sgi.com \
--to=prarit@sgi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.