[CentOS-devel] RH patches v/s vanilla docker in CentOS

On Wed, Apr 29, 2015 at 07:16:30PM -0400, Jason Brooks wrote:
> 
> 
> ----- Original Message -----
> > From: "Jason Brooks" <jbrooks at redhat.com>
> > To: "The CentOS developers mailing list." <centos-devel at centos.org>
> > Sent: Wednesday, April 29, 2015 4:04:52 PM
> > Subject: Re: [CentOS-devel] RH patches v/s vanilla docker in CentOS
> > 
> > 
> > 
> > ----- Original Message -----
> > > From: "Lokesh Mandvekar" <lsm5 at fedoraproject.org>
> > > To: "The CentOS developers mailing list." <centos-devel at centos.org>
> > > Sent: Wednesday, April 22, 2015 9:07:12 AM
> > > Subject: Re: [CentOS-devel] RH patches v/s vanilla docker in CentOS
> > > 
> > 
> > ...
> > > 
> > > Given the conflicting requirements, would it make sense to have appropriate
> > > tags such that, a particular 'docker' (something with RH patches) build
> > > only
> > > makes it to atomic, while another 'docker' build makes it to virt7-release
> > > (only upstream docker sources)
> > 
> > +1
> > 
> > I think it makes sense for everything atomic needs to live in atomic7,
> > and if atomic wants the same version as virt has, great, if not, atomic
> > could have its own.
> 
> I just tried a tree compose w/ docker-master, but it Provides 
> docker-io, not docker, so yum's trying to pull in plain "docker"
> as well, which conflicts...

Ah ok, I can update it to 'Provides: docker' as well. But would that help solve
the conflict or would it still get confused between 'docker' and
'docker-master'. Maybe, docker-master deserves to be in a separate tag,
virt7-nightly perhaps??

> 
> > 
> > Jason
> > 
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel at centos.org
> http://lists.centos.org/mailman/listinfo/centos-devel

-- 
Lokesh
Freenode, OFTC: lsm5
GPG: 0xC7C3A0DD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20150430/e28e64a7/attachment-0004.sig>