[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#460504: dh_desktop/dh_icons madness



On dim, 2008-01-13 at 12:15 +0100, Peter Eisentraut wrote:
> Josselin Mouette wrote:
> > Debian has always been about integration. Don’t you register your
> > documentation with doc-base so that your application integrates with
> > centralized documentation systems?
> 
> I'm glad you bring up this comparison, but this is different.  If someone 
> neglects to do doc-base registration, his package's documentation won't be 
> usable in a nice way.  That directly affects the functionality of that 
> package.  If someone doesn't do dh_icons or dh_desktop registration, nothing 
> changes for that package.  It affects only users of whatever environment it 
> is that appears to require this.

You are completely wrong on this topic. If you don’t use dh_icons, the
icons shipped in your package won’t be available even to the application
itself. This is caused by a broken design for icon caches; because of
this design, icon caches are currently disabled. But when all packages
have been ported to update the cache, icons shipped in packages not
doing it won’t be available all (whether the application uses Qt or
GTK).

> > It is not a random user environment. It is the accepted standard for the
> > three main desktops we are shipping.
> 
> I assume you are talking about GNOME, Xfce, and KDE here.  KDE doesn't do any 
> of this, so have doubts about the "accepted standard".  It seems silly to 
> request all KDE-related packages to jump through hoops so they work with 
> GNOME.

KDE already uses the freedesktop standard for the menus. If it doesn’t
use it for the MIME registry as well, I would be very surprised if
upstream didn’t have at least plans to do that.

> It is to the desktop environment's benefit.  The package will work fine in 
> other environments.  To pick a concrete example (bug #460449), if a GNOME 
> user clicks on a kdissert file and things don't work, while they work just 
> fine in KDE, then that is GNOME's problem, not kdissert's.

In fact I am very surprised KDE doesn’t need the desktop database to be
up-to-date. Scanning all desktop files at runtime is deadly slow, so
even in this case it is a bad idea not to update the cache. Which is why
this is also probably affecting KDE users.

> > I thought dpkg triggers had been sufficiently advertised, but it seems
> > the mails haven’t reached the (deep ?) place you are living in.
> 
> They indeed haven't, but since they appear to have reached the (shallow ?) 
> place you are living in, why not use them?

If you had read them, you would also know this feature isn’t available
yet.

-- 
 .''`.
: :' :      We are debian.org. Lower your prices, surrender your code.
`. `'       We will add your hardware and software distinctiveness to
  `-        our own. Resistance is futile.

Attachment: signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=


Reply to: