SCIENTIFIC-LINUX-USERS Archives

September 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Patrick J. LoPresti" <[log in to unmask]>
Reply To:
Patrick J. LoPresti
Date:
Tue, 2 Sep 2014 14:21:45 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
On Tue, Sep 2, 2014 at 2:11 PM, Pat Riehecky <[log in to unmask]> wrote:
>
> The sources were taken from git.  They were then compared to the sources
> from the public Release Candidate provided by upstream on April 22 2014.
> There were very few changes from this Release Candidate to the official
> release.

Nice work.

> All the Security/Enhancement/Bugfix code comes out of git as the source rpms
> for these were never publicly released.

Does this mean there is no way to correlate security/bugfix updates
from Red Hat with the changes in git, and therefore no way to know how
far SL is diverging from RHEL over time?

Is the git tree entirely RHEL + released updates, or are unreleased
CentOS changes mixed in as well?

Presumably, anyone with a RHEL subscription (and the right tools)
could compare the git repository against the update SRPMs, at least to
tell you whether they are the same. Would that be a violation of the
subscription terms, I wonder?

Just curious.

 - Pat

ATOM RSS1 RSS2