On 07/02/2014 02:01 PM, Les Mikesell wrote: > On Wed, Jul 2, 2014 at 1:31 PM, Manuel Wolfshant > <wolfy at nobugconsulting.ro> wrote: >>> On Wed, Jul 2, 2014 at 9:40 AM, Karanbir Singh <mail-lists at karan.org> >>> wrote: >>>> [1]: which we are not, since we always try and match 1:1 with >>> upstream >>>> release media >>> If you aren't consuming upstream src rpms from their repositories any >>> more, will you still actually know that you have a 1:1 match? >> We consume the same sources as before. Just that instead of being pushed by RH to the world as src.rpm we have the content (still pushed by RH !) already exploded. Incidentally this happens in a convenient git environment. > I don't understand how that relates to the upstream release packaging, > though. Is there a way to distinguish something included in a future > 7.1 release and a subsequent 0-day update? Or do you have to check > the package versioning against their release? We always have to check it against the release .. there are several different repos that we crunch into one (Server, Server-Optional, Workstation, Workstation-Optional, Client, Client-Optional, HPCNode, HPCNode-Optional, etc). The whether the list of SRPMs is in a directory or in GIT .. it is all the same stuff in one spot. For example: ftp://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/ That is a list of all the SRPMS ... they have a list in all the other things too .. 6Client, 6Workstation, 6Node .. we combine them all into one big set of unique SRPMs and build them all. Same thing in git .. all the versions are there, imported. The difference is, in git you can roll back to whatever version you want, all in one spot, see the specs and sources already exploded, edit them if required, etc. We always also need to look at the compilation of those binaries to match up the isos, etc. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20140702/f46ae78f/attachment-0007.sig>