public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gilles Dartiguelongue <eva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] gnome2-utils.eclass add support for gdk-pixbuf cache update
Date: Wed, 04 Sep 2013 20:57:41 +0200	[thread overview]
Message-ID: <1378321061.3843.9.camel@kanae> (raw)
In-Reply-To: <1378048230.4845.1.camel@kanae>

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.

-- 
Gilles Dartiguelongue <eva@gentoo.org>
Gentoo



  reply	other threads:[~2013-09-04 18:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-31 11:07 [gentoo-dev] [PATCH] gnome2-utils.eclass add support for gdk-pixbuf cache update Gilles Dartiguelongue
2013-08-31 11:40 ` Michał Górny
2013-08-31 13:00   ` Gilles Dartiguelongue
2013-08-31 13:30     ` Alex Xu
2013-08-31 14:49     ` Michał Górny
2013-08-31 16:44       ` Gilles Dartiguelongue
2013-09-01 11:29         ` Gilles Dartiguelongue
2013-09-01 12:11           ` Michał Górny
2013-09-01 15:10             ` Gilles Dartiguelongue
2013-09-04 18:57               ` Gilles Dartiguelongue [this message]
2013-09-04 19:23                 ` Ian Stakenvicius
2013-09-04 19:44                   ` Gilles Dartiguelongue
2013-09-04 19:48                     ` Ian Stakenvicius
2013-09-04 19:49                       ` Ian Stakenvicius
2013-09-04 20:19                       ` Gilles Dartiguelongue
2013-09-04 20:21                         ` Ian Stakenvicius
2013-09-04 20:51                         ` Michał Górny
2013-09-10  0:29                         ` Gilles Dartiguelongue
2013-09-09 23:18                           ` hasufell
2013-09-09 23:31                           ` Alex Xu
2013-09-10 10:22                             ` Ian Stakenvicius
2013-09-10 15:10                               ` Fabian Groffen
2013-09-11  8:51                                 ` Gilles Dartiguelongue
2013-09-11  8:23                                   ` Fabian Groffen
2013-09-04 20:07                     ` Zac Medico
2013-09-04 19:56                 ` Michał Górny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1378321061.3843.9.camel@kanae \
    --to=eva@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox