Summary: | gnome-extra/gconf-cleaner-0.0.3 (New package) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Luca Marturana <lucamarturana> |
Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | RESOLVED OBSOLETE | ||
Severity: | enhancement | CC: | gnome, jlec, turkalinux, vyacheslavovich |
Priority: | Low | Keywords: | EBUILD |
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://code.google.com/p/gconf-cleaner/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
gconf-cleaner-0.0.2.ebuild
gconf-cleaner-0.0.2.ebuild gconf-cleaner-0.0.3.ebuild |
Description
Luca Marturana
2007-05-08 17:11:23 UTC
Created attachment 118583 [details]
gconf-cleaner-0.0.2.ebuild
This tool is _dangerous_ and unless upstream Gnome sees interest in it, I doubt any of us will add it in portage. First of all, some gnome software don't use gconf schemas at all or have incomplete schemas for practical reasons (NetworkManager comes to mind). This won't be detected and can break stuff. Second, we don't "uninstall" old gconf schemas when a package is removed (for historical reasons, maybe we'll do it later). So old stuff might even still be tied to a schema that isn't there anymore. Given these arguments, I still encourage you to post updated ebuilds here for others to find, while gconf-cleaner matures a little :) Thanks for posting your work here. (In reply to comment #2) OK, I understand and agree to your reasons. ;) Created attachment 123178 [details]
gconf-cleaner-0.0.2.ebuild
Added ~amd64 keywords
Created attachment 161962 [details]
gconf-cleaner-0.0.3.ebuild
Bump to gconf-cleaner-0.0.3 align ebuild requests to same values Bump request Again, we still don't feel convinced by the benefits of this tool over the damages it can cause. Feel free to update the ebuild here or to have it included in Sunrise. Thanks RESOLVED as OBSOLETE since there is no update and package is not in tree Coordinated with leio |