We should really move further discussion to the deploy-users list, as it is a separate project. But briefly, deploy makes it easy both to create the _big_list_of_packages, and to automate testing, installation, and updates using it. We keep a repository of physical packages (rather than just a list of package names/versions/repo_locations) both because it is easier to work with and because we create some packages automatically as we go. The differences between repository versions could be optimized for disk space usage using hardlinks, and this is something we have considered and could implement relatively easily.... -----Original Message----- From: centos-devel-bounces at centos.org [mailto:centos-devel-bounces at centos.org] On Behalf Of Les Mikesell Sent: Tuesday, April 22, 2014 12:59 PM To: The CentOS developers mailing list. Subject: Re: [CentOS-devel] ostree as a delivery model On Tue, Apr 22, 2014 at 1:54 PM, Kay Williams <kay at deployproject.org> wrote: > You would use deploy to create an individual repository (mini spin) > for each server. At that point, content would be frozen. So you do have to keep a frozen copy of every state that you might want to reproduce later? Instead of just tracking package versions? >When you wanted to update > the repository for that server, you would run deploy again to >integrate, test and release new packages. I'm missing how this is supposed to make things easier or better than a 'yum install _big_list_of_packages_'. -- Les Mikesell lesmikesell at gmail.com _______________________________________________ CentOS-devel mailing list CentOS-devel at centos.org http://lists.centos.org/mailman/listinfo/centos-devel