> 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]
>
>
How bout simply subscribing to the announce-list and reading your email
about the newest errata releases. I seem to recall them being announced
there.
Then beginning with cartman theres the "update agent".
These two along with the present errata pages seem to address the
concerns and issues you have raised.
I dont see how taking the additional time to create some sort of "new
package" of RPMS for consumers is better than the current tools
available. A large "package" of RPMS seems to me to be redundant and not
bandwidth friendly.
Each errata release has a date of release, a detailed explaination and a
version number. Any user can simply use RPM to determine the version tey
have intalled. The total time needed is quite minimal. Then thers the
"Update Agent" which I beleive to be quite self explanitory and defeats
te purpose of maintaining a seperate "package" that you describe.
I don't see the current avenues as being utilized in your scenario.
Respectfully,
Scott
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
