[Yum-devel] [PATCH] add the btrfs-snapshot plugin to yum-utils

[James Antill]

On Thu, 2009-12-10 at 09:14 -0500, Josef Bacik wrote:

> > 4. Accessing ts.po.dirlist for a "remote" package means the user needs
> > to download the filelist MD. This isn't easy to fix :(.
> >
> 
> I guess the same thing goes for po.filelist and such right?

 Yeh, the only way to get around it is to wait until post download time
(pretrans_hook covers this) and then use localPkg() and reopen each of
the packages as new YumLocalPackage(), reading the filelist data
directly from the rpms ... which sucks in many ways.

> > 5. You don't take bind() mounts into account
> 
> Somebody always has to bring up bind() mounts ;).  I will see what can
> be done about this.

 Yeh, even worse I think you have to take symlinks into account ... and
I don't think you can do that without going insane. The "best" way would
be a new API for rpm which tells us which mount points it's going to
write too when we do the test transaction -- as it needs to do basically
this test for the disk space check.

> So the idea here is if the user setup a different subvolume for /home
> that they don't necessarily want /home snapshotted every time they do
> an update.  Packages shouldn't be touching users home directory right?
>  I guess it wouldn't be terrible to do everything, and it would
> certainly make things simpler, I'll have to think about it.

 Yeh, I understood that ... the problem is that although
Fedora/RHEL/etc. will probably never produce rpms that run scriplets
which alter /home, you can't guarantee that of random rpm producers :(.