-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 04/09/13 03:44 PM, Gilles Dartiguelongue wrote:
> Le mercredi 04 septembre 2013 à 15:23 -0400, Ian Stakenvicius a
> écrit : [snip]
>>
>> By gdk-pixbuf.cache , you mean the 'loaders.cache' file that the
>> eclass is now continuously updating? Which ebuild is going to
>> 'own' it?
>
> yes, gdk-pixbuf is going to own it since it is the main loader
> provider and the package that provides the tool to generate the
> cache.
>
>> 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.
>
> it is not owned by any package right now but touching the file in
> src_install made collision-protect abort the install.
You had FEATURES="collision-protect" enabled" or the default
FEATURES="protect-owned" ?
>
>> 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?
>
> That sounds like a good idea, I guess it does not cause a
> collision-protect error because the file is added to ${D} after
> comparison between ${D} and live file-system ?
>
No, it still does collide that first time if
FEATURES="collision-protect" is enabled. In fact, I do not believe
there is (by design) any way for this ebuild to 'take ownership' of a
file it doesn't already own without user intervention, if
FEATURES="collision-protect" is enabled.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iF4EAREIAAYFAlInjogACgkQ2ugaI38ACPBzyQD9E6d71+zINTn6GWPPmOJHJL0I
K4IWNlanJJVE5WNpypkA/1bB1iYGQuVZIok1IssaGinme1FyJeUnDHy9PaXQTdTt
=sPlK
-----END PGP SIGNATURE-----
