SCIENTIFIC-LINUX-USERS Archives

June 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:
Thu, 19 Jun 2014 08:38:47 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
On Thu, Jun 19, 2014 at 6:00 AM, Lamar Owen <[log in to unmask]> wrote:
>
> If the spec, patches, and sources are all committed with the same commit ID

Has Red Hat made any commitment to operate in this fashion?

If not, why would you assume this?

> for a particular package, you can grab the updated spec file (using the
> commit feeds), pull the NEVRA info out of it

As Nico points out, this is assuming regularity and meaning in the
NEVRA values that are tenuous at best. Has Red Hat made any commitment
to provide such regularity and meaning? If not, why would you assume
them?

> Those procedures are being written even as we speak, and patches are being
> applied to the CentOS git repo.  SL developers are involved in the process.

Yes, I have been following the CentOS lists. It sounds like a huge
pain in the butt and extremely fragile besides.

Red Hat could make it trivial and completely robust, with zero effort,
simply by tagging the repositories. Why don't they do that, I wonder?

 - Pat

ATOM RSS1 RSS2