> Service packs are an interesting notion. This has been debated internally.
> Currently, fixes and updates are turned out by devel as soon as the
> individual package is fixed. Announcements are made on the
> redhat-announce-list, are put up on the support website asap, and put on
> the main ftp server.
>
> Would rather have a monolithic blob of patches released as soon as its
> ready, or individual packages that address specific problems that are
> released as soon as they are fixed? I personally opt for the latter.
Maybe there is a third solution..... a combination of the both
perhaps you could keep the errata section of the redhat website, and also
have a service release section... that way people like myself who go to
the errata section and see a huge ammount of files, and are a tad unsure
of what there doing can go for the service release every few months and
download all the fixes in one huge rpm maybe :] (can rpm's contain several
rpms ??)
If that was the case, it would only mean throwing the current rpms from
the last service release into a file and posting it - which to me sounds
like a dream for the consumer. specially people who want to have things
fixed properly, but cant spare the time to go searching for updated files
in directory every day to see whats new.
Might be an idea to think about maybe
Matt
[EMAIL PROTECTED]
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
