Re: Is there any way to delete old commits?

[Jonathan Dieter <jdieter lesbg com>]

On 02/02/2015 09:30 PM, Colin Walters wrote:
> Note that OSTree's an object store, so commits basically
> only store "new objects" (modified or new files, plus some fixed metadata
> overhead).
>
> But yes, at some point it does grow large, and you don't need to carry
> the history.  Something crucial to note is that you can at any point
> just blow away a repository and create it fresh, and clients can update
> from it.  All the client cares about is finding a commit with a newer
> timestamp.

That's great.  And the clients will only download files that have 
changed, right?

> However, there are uid/gid issues to keep in mind; see
> the passwd/group related options here:
> https://github.com/projectatomic/rpm-ostree/blob/master/doc/treefile.md

I was actually planning to just use plain ostree and use yum 
--installroot=foo because most of my configuration is via ansible and 
rpm-ostree seems to have limited support for post-rpm configuration (the 
bit about it running in a non-networked container seems to make using 
ansible a bit difficult).

Is this a foolish plan?  Should I be doing what I can to make rpm-ostree 
work?

> I just filed:
> https://bugzilla.gnome.org/show_bug.cgi?id=743882

Thanks much.  That looks like it's exactly what I'm looking for.

And thanks for putting this all together.  It was your talk at 
DevConf.cz last year that inspired me to try to make this work.

Jonathan