On Tue, Apr 22, 2014 at 5:22 PM, Kay Williams <kay at deployproject.org> wrote: > 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.... So even if you had dozens of deployments differing only by a few packages you would still require a full copy of everything in each of those states - kept for as long as you might want another deployment? I was hoping to find something that started with a more sensible premise. -- Les Mikesell lesmikesell at gmail.com