Hi guys,
I made my first namcap module yesterday and i want to work more on this. Unfortunately i did not found any TODO list for it, so i want to hear from you guys: what you want to see on namcap? Any idea for a module or feature?
-- Hugo
Am Donnerstag 22 Januar 2009 15:22:59 schrieb Hugo Doria:
Hi guys,
I made my first namcap module yesterday and i want to work more on this. Unfortunately i did not found any TODO list for it, so i want to hear from you guys: what you want to see on namcap? Any idea for a module or feature?
-- Hugo
Do we have the info pages stuff implemented already? Another nice-to-have would be to detect if the package conatains hicolor icons or new mime-types ( see http://bugs.archlinux.org/task/11023)
Then you'll need an install script like this: http://repos.archlinux.org:80/viewvc.cgi/kdelibs/trunk/kdelibs.install?revis...
Note: the mime and icon stuff is independend from each other.
On Thu, Jan 22, 2009 at 9:29 AM, Pierre Schmitz pierre@archlinux.de wrote:
Am Donnerstag 22 Januar 2009 15:22:59 schrieb Hugo Doria:
Hi guys,
I made my first namcap module yesterday and i want to work more on this. Unfortunately i did not found any TODO list for it, so i want to hear from you guys: what you want to see on namcap? Any idea for a module or feature?
-- Hugo
Do we have the info pages stuff implemented already? Another nice-to-have would be to detect if the package conatains hicolor icons or new mime-types ( see http://bugs.archlinux.org/task/11023)
Then you'll need an install script like this: http://repos.archlinux.org:80/viewvc.cgi/kdelibs/trunk/kdelibs.install?revis...
Note: the mime and icon stuff is independend from each other.
--
namcap could return a warning if man pages are installed in /usr/man instead of /usr/share/man. the same could be done for info files: (/usr/info instead of /usr/share/info).
Eric Bélanger wrote:
On Thu, Jan 22, 2009 at 9:29 AM, Pierre Schmitz pierre@archlinux.de wrote:
Am Donnerstag 22 Januar 2009 15:22:59 schrieb Hugo Doria:
Hi guys,
I made my first namcap module yesterday and i want to work more on this. Unfortunately i did not found any TODO list for it, so i want to hear from you guys: what you want to see on namcap? Any idea for a module or feature?
-- Hugo
Do we have the info pages stuff implemented already? Another nice-to-have would be to detect if the package conatains hicolor icons or new mime-types ( see http://bugs.archlinux.org/task/11023)
Then you'll need an install script like this: http://repos.archlinux.org:80/viewvc.cgi/kdelibs/trunk/kdelibs.install?revis...
Note: the mime and icon stuff is independend from each other.
--
namcap could return a warning if man pages are installed in /usr/man instead of /usr/share/man. the same could be done for info files: (/usr/info instead of /usr/share/info).
I believe namcap does this for /usr/man but not for /usr/info. It does complain about the /usr/share/info/dir file.
Allan
On Thu, Jan 22, 2009 at 8:22 AM, Hugo Doria hugodoria@gmail.com wrote:
Hi guys,
I made my first namcap module yesterday and i want to work more on this. Unfortunately i did not found any TODO list for it, so i want to hear from you guys: what you want to see on namcap? Any idea for a module or feature?
I was thinking it might actually be nice to add some informational output too. Instead of just errors or warnings, output things like the size of docs and other info we might find useful in making decisions about the PKGBUILD itself.
On Thu, Jan 22, 2009 at 11:08 AM, Aaron Griffin aaronmgriffin@gmail.com wrote:
On Thu, Jan 22, 2009 at 8:22 AM, Hugo Doria hugodoria@gmail.com wrote:
Hi guys,
I made my first namcap module yesterday and i want to work more on this. Unfortunately i did not found any TODO list for it, so i want to hear from you guys: what you want to see on namcap? Any idea for a module or feature?
I was thinking it might actually be nice to add some informational output too. Instead of just errors or warnings, output things like the size of docs and other info we might find useful in making decisions about the PKGBUILD itself.
This is a good idea. Right now -i won't work for that. -i outputs something that's more like debugging info. We could always expand the number of outputs for modules from 3 (Error, Warning, Info) to 4 (Error, Warning, Info, Debug) where Info would actually be helpful.
Jason
On Fri, Jan 23, 2009 at 20:30, Jason Chu jason@archlinux.org wrote:
This is a good idea. Right now -i won't work for that. -i outputs something that's more like debugging info. We could always expand the number of outputs for modules from 3 (Error, Warning, Info) to 4 (Error, Warning, Info, Debug) where Info would actually be helpful.
Jason
I like the expansion of verbosity levels. Big +1 from me here on this and the other changes mentioned.
arch-dev-public@lists.archlinux.org