Bug 284853 - Shipping of ktelepathy.notifyrc
Summary: Shipping of ktelepathy.notifyrc
Status: RESOLVED FIXED
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: git-latest
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: 0.5-next
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks: 298733
  Show dependency tree / graph
 
Reported: 2011-10-24 09:29 UTC by Martin Klapetek
Modified: 2012-08-27 21:13 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Klapetek 2011-10-24 09:29:47 UTC 
Version:           git-latest
OS:                Linux

Currently we ship the .notifiyrc file with contact list, but if you install kded-module and not contact list, error handler won't work, because it misses the .notifyrc file. Since there is also some effort to create a plasmoid version of contact list, I think the .notifyrc should be installed as part of the "integration daemon", that is kded-module (notification popups are 'integration' anyway).

What do you think?

Reproducible: Always



Expected Results:
Comment 1 David Edmundson 2011-10-24 10:03:24 UTC 
Seems like effort to move it now, once we have a library it should go in there, no point moving things again and again.
Comment 2 Daniele E. Domenichelli 2012-03-22 13:51:10 UTC 
Now that we have a library we should move this, and perhaps also the icons to ktp-common-internals
Comment 3 David Edmundson 2012-04-03 23:34:45 UTC 
This is pending some complex discussion about moving translations. See George K for details
Comment 4 Adrián Chaves (Gallaecio) 2012-08-26 18:01:38 UTC 
Can this be closed?
Comment 5 Martin Klapetek 2012-08-27 08:22:23 UTC 
This has been closed for months (as have been others where you asked this). Please always check the status first.

Thanks for the triaging though ;)
Comment 6 Adrián Chaves (Gallaecio) 2012-08-27 21:01:57 UTC 
Well, I meant CLOSED as opposed to RESOLVED. I guess you are not using CLOSED (yet?) either.
Comment 7 Martin Klapetek 2012-08-27 21:13:22 UTC 
Ah, I see. No, we're not. We have ~700 RESOLVED bugs and I personally think that such status is enough, I don't see the point in changing from RESOLVED to CLOSED (and also I don't want to spam with 700 email marking all RESOLVED bugs as CLOSED).