Re: [arch-general] Patch for update-mime-info slowness

2013-12-06 Thread Alexander Rødseth
Yet another option is to fork shared-mime-info and upload an AUR package for the fork. If upstream WONTFIX an issue that several people perceive to be a bug, or WONTFIX a popular feature request, they should be aware that someone forking the project is a real possibility. Such are they perils and j

Re: [arch-general] Patch for update-mime-info slowness

2013-12-06 Thread Lukas Jirkovsky
On Thu, Dec 5, 2013 at 8:39 PM, Timothée Ravier wrote: > > How could this not qualify for a bug report? Because it may be an intended feature (and it looks so). In that case it's IMO better discuss it before filling bug reports, otherwise it often generates the "WONTFIX" kind of reports. However

Re: [arch-general] Patch for update-mime-info slowness

2013-12-06 Thread Gaetan Bisson
[2013-12-06 01:14:08 -0500] Sébastien Leblanc: > I was not > looking to file a bug, or anything. I am only sharing a patch with > fellow Arch users. Then why did you Cc the maintainer of this package? I'm not insisting that bug reports and feature requests be submitted to our tracker just to make

Re: [arch-general] Patch for update-mime-info slowness

2013-12-06 Thread Sébastien Leblanc
On Thu, Dec 5, 2013 at 7:37 PM, Gaetan Bisson wrote: > [2013-12-04 15:00:31 -0500] Sébastien Leblanc: >> I am kind of annoyed by the time it takes to update the MIME database > > Please, please, please. Bug reports and feature requests go to: Thank you, I already know the URL to the bug tracker,

Re: [arch-general] Patch for update-mime-info slowness

2013-12-05 Thread Allan McRae
On 06/12/13 05:39, Timothée Ravier wrote: > On 05/12/2013 20:10, Lukas Jirkovsky wrote: >> On Thu, Dec 5, 2013 at 7:37 PM, Gaetan Bisson wrote: >>> [2013-12-04 15:00:31 -0500] Sébastien Leblanc: I am kind of annoyed by the time it takes to update the MIME database >>> >>> Please, please, plea

Re: [arch-general] Patch for update-mime-info slowness

2013-12-05 Thread Timothée Ravier
On 05/12/2013 20:10, Lukas Jirkovsky wrote: > On Thu, Dec 5, 2013 at 7:37 PM, Gaetan Bisson wrote: >> [2013-12-04 15:00:31 -0500] Sébastien Leblanc: >>> I am kind of annoyed by the time it takes to update the MIME database >> >> Please, please, please. Bug reports and feature requests go to: > >

Re: [arch-general] Patch for update-mime-info slowness

2013-12-05 Thread Armin K.
On 5.12.2013 20:10, Lukas Jirkovsky wrote: On Thu, Dec 5, 2013 at 7:37 PM, Gaetan Bisson wrote: [2013-12-04 15:00:31 -0500] Sébastien Leblanc: I am kind of annoyed by the time it takes to update the MIME database Please, please, please. Bug reports and feature requests go to: I'm not sure

Re: [arch-general] Patch for update-mime-info slowness

2013-12-05 Thread Lukas Jirkovsky
On Thu, Dec 5, 2013 at 7:37 PM, Gaetan Bisson wrote: > [2013-12-04 15:00:31 -0500] Sébastien Leblanc: >> I am kind of annoyed by the time it takes to update the MIME database > > Please, please, please. Bug reports and feature requests go to: I'm not sure whether this should classify as a bug rep

Re: [arch-general] Patch for update-mime-info slowness

2013-12-05 Thread Gaetan Bisson
[2013-12-04 15:00:31 -0500] Sébastien Leblanc: > I am kind of annoyed by the time it takes to update the MIME database Please, please, please. Bug reports and feature requests go to: https://bugs.archlinux.org/ Not this list, not private emails to maintainers, not a combination of the ab

Re: [arch-general] Patch for update-mime-info slowness

2013-12-05 Thread Rodrigo Rivas
On Wed, Dec 4, 2013 at 9:00 PM, Sébastien Leblanc wrote: > I am kind of annoyed by the time it takes to update the MIME database > (something like two minutes on a recent i7 quad-core laptop). Until > pacman has hooks/triggers, I have removed the calls to fdatasync > (which are supposed to ensure

[arch-general] Patch for update-mime-info slowness

2013-12-04 Thread Sébastien Leblanc
I am kind of annoyed by the time it takes to update the MIME database (something like two minutes on a recent i7 quad-core laptop). Until pacman has hooks/triggers, I have removed the calls to fdatasync (which are supposed to ensure that the files are truly written to disk). I prefer letting the sy