Michael Biebl wrote:
[...]
It's also a matter for what case we optimize:
For users running unstable, who constantly update, it might/will happen
that the update-desktop-database trigger is activated although
unnecessary.
For stable users, who only do distro upgrades, it might be quite
Josselin Mouette wrote:
As for update-mime-database, I think it concerns only a very small
number of packages, but that’s certainly doable.
I've looked into update-mime-database and update-mime. Here's what I think needs
to be done in order to properly adopt triggers support in these packages:
Michael Biebl wrote:
See /usr/share/doc/dpkg-dev/triggers.txt.gz, w.r.t file triggers.
The trigger will one be run if it matches a file (e.g. /usr/share/icons or
/usr/share/applications).
James Vega wrote:
The whole point of triggers is that they watch a set of
files/directories and when
Mike Hommey wrote:
On Tue, Feb 10, 2009 at 12:03:27PM +0100, Loïc Minier wrote:
On Tue, Feb 10, 2009, Josselin Mouette wrote:
I don’t think it’s a good idea to use triggers for
update-desktop-database. There are many .desktop files without a
MimeType key, and for all of them calling
Le mardi 10 février 2009 à 19:27 +0100, Michael Biebl a écrit :
Josselin Mouette wrote:
For update-icon-caches, that was the plan when introducing it. However
it can only apply to the hicolor and gnome themes. Other themes will
still need to call dh_icons. This also means dh_icons will have
Le dimanche 08 février 2009 à 18:34 -0800, Russ Allbery a écrit :
I removed the requirement to call dh_desktop every time you have a
*.desktop file. I didn't remove the tag entirely since at the time we had
no triggers and you still did need to call update-desktop-database if the
*.desktop
On Tue, Feb 10, 2009, Josselin Mouette wrote:
I don’t think it’s a good idea to use triggers for
update-desktop-database. There are many .desktop files without a
MimeType key, and for all of them calling update-desktop-database is a
waste of time.
On my system, only 30% of .desktop files
Le mardi 10 février 2009 à 12:03 +0100, Loïc Minier a écrit :
sudo update-desktop-database -q 0,06s user 0,02s system 96% cpu 0,075 total
I didn’t recall it was that cheap. The trigger is then definitely the
way to go.
--
.''`.
: :' : We are debian.org. Lower your prices, surrender
Josselin Mouette wrote:
Le mardi 10 février 2009 à 12:03 +0100, Loïc Minier a écrit :
sudo update-desktop-database -q 0,06s user 0,02s system 96% cpu 0,075 total
I didn’t recall it was that cheap. The trigger is then definitely the
way to go.
Joss, what's your opintion on
Le mardi 10 février 2009 à 13:34 +0100, Michael Biebl a écrit :
Joss, what's your opintion on update-mime-database (dh_installmime) and
update-icon-caches (dh_icons)?
Should we triggerize them too?
As for update-mime-database, I think it concerns only a very small
number of packages, but
Josselin Mouette wrote:
Le mardi 10 février 2009 à 13:34 +0100, Michael Biebl a écrit :
Joss, what's your opintion on update-mime-database (dh_installmime) and
update-icon-caches (dh_icons)?
Should we triggerize them too?
For update-icon-caches, that was the plan when introducing it.
On Tue, Feb 10, 2009 at 12:03:27PM +0100, Loïc Minier wrote:
On Tue, Feb 10, 2009, Josselin Mouette wrote:
I don’t think it’s a good idea to use triggers for
update-desktop-database. There are many .desktop files without a
MimeType key, and for all of them calling update-desktop-database is
Russ Allbery wrote:
Loïc Minier l...@dooz.org writes:
I can see how it would be useful to recommend calling dh_desktop as
soon as you distribute .desktop files just like it would be more useful
if we could inject any rules in packages via cdbs or the new dh.
However, this is really
Michael Biebl wrote:
Maybe i missinterpreted your conclusion, but this what I get in one of my
packages:
desktop-mimetype-without-update-call /usr/share/applications/...
Now that we have triggers, I really don't see the benefit of adding such a
lintian warning. Imho we should get rid of
On Sun, Feb 08, 2009 at 09:21:10PM +0100, Emilio Pozuelo Monfort wrote:
Michael Biebl wrote:
Maybe i missinterpreted your conclusion, but this what I get in one of my
packages:
desktop-mimetype-without-update-call /usr/share/applications/...
Now that we have triggers, I really don't
Emilio Pozuelo Monfort wrote:
Michael Biebl wrote:
Maybe i missinterpreted your conclusion, but this what I get in one of my
packages:
desktop-mimetype-without-update-call /usr/share/applications/...
Now that we have triggers, I really don't see the benefit of adding such a
lintian
Michael Biebl bi...@debian.org writes:
Russ Allbery wrote:
Okay, that matches my reasoning. I'll remove that tag in the next
version of Lintian. Thank you very much!
Maybe i missinterpreted your conclusion, but this what I get in one of
my packages:
desktop-mimetype-without-update-call
On Sun, Dec 28, 2008, Russ Allbery wrote:
1. The update-desktop-database program used to be documented in the
desktop entry spec in version 0.9.5 and was removed in 0.9.6 (the
current version is 1.0). Should I draw some conclusion from that? Is
this program and cache likely to go
Loïc Minier l...@dooz.org writes:
(I have no idea why it's not mentionned anymore.) Yes, the program is
still used; it's in charge of generating
/usr/share/applications/mimeinfo.cache (and
/usr/local/share/applications/mimeinfo.cache); these files may then be
used by e.g. gio (in
Hello all,
I started looking today in more depth at the MIME type registration
process for applications providing *.desktop files, dh_desktop, and what
Lintian is currently doing (as part of addressing #488832).
Current situation: Lintian warns of packages that contain desktop files in
the
Hi Russ.
Russ Allbery r...@debian.org (28/12/2008):
I started looking today in more depth at the MIME type registration
process for applications providing *.desktop files, dh_desktop, and
what Lintian is currently doing (as part of addressing #488832).
With (or without, not sure) my submitter
21 matches
Mail list logo
