On 07/02/2014 08:01 PM, Les Mikesell wrote:
On Wed, Jul 2, 2014 at 1:31 PM, Manuel Wolfshant wolfy@nobugconsulting.ro wrote:
On Wed, Jul 2, 2014 at 9:40 AM, Karanbir Singh mail-lists@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?
All the content went into a single directory earlier as well, now its git. and the distro is still '7'
I think one issue that is clear is that lots of people were working under or just assuming context that never existed, because either its not something they interacted with -or- they didnt need to.
nutshell: git.c.o has the same content, in an easier to consume manner and an easier to track and trace format.