-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 04/09/13 02:57 PM, Gilles Dartiguelongue wrote:
> One last point to handle, how to migrate gdk-pixbuf.cache so that
> it is owned by the ebuild ?
>
> I've discussed this with Michał and it seems two options are
> possible.
>
> 1. rm the file on the filesystem in pkg_preinst in gdk-pixbuf
> ebuild pros: - works immediately without fiddling with profiles
> (see 2) cons: - no idea what PMS says about it, Michał told me it
> shouldn't work yet my testing proves otherwise. - leaves the system
> with no loaders.cache for a while which could result in apps
> starting with no lots of missing icons.
>
> 2. use COLLISION_IGNORE in profiles/base/make.conf pros: - does not
> leave the system without the cache file cons: - add a setting to
> base/make.conf for a long period of time to ensure most of our user
> have migrated (how long would it be btw, 6 months, 1 year ?) - does
> not protect other packages from owning the package due to this very
> solution for the time the setting is left in base/make.conf
>
> 3. write a news item and let users handle it
>
>
> Is there any other solution or is there any other point that would
> move the balance from one solution to another ?
>
> This solution would also be applied to a couple of other commonly
> regenerated files in Gnome ebuilds, like gtk-icon-cache, etc.
>
By gdk-pixbuf.cache , you mean the 'loaders.cache' file that the
eclass is now continuously updating? Which ebuild is going to 'own' it?
Also, is it owned by anything right now? IIRC we don't try
particularly hard to support FEATURES="collision-protect" in the tree,
but rather FEATURES="protect-owned", and so if the file is currently
sitting there unowned by any package, afaik you shouldn't get any
collisions by installing over it.
If you want to do that *and* maintain whatever is currently in that
file, you can use the trick sys-apps/openrc used to do: in
pkg_preinst, copy the system file (if it exists) into ${D}, and then
let that same copy be merged back into the system. Openrc did it to
get around CONFIG_PROTECT, but it had the unfortunate side effect of
making the package own the file. I don't know if removal will be
affected by this though if the contents of the file change after the
ebuild owning it was merged?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iF4EAREIAAYFAlIniLAACgkQ2ugaI38ACPA1gwD/ZRbX/aD+S/SOMHrvPsKJ6S7/
0Dvyq7FDPGpVwPXPLIAA/iYpLP4SbLowsFqGWOhyNB6FdAS93TOmoy5MNKHddocc
=9Xqu
-----END PGP SIGNATURE-----
