Bug 214824 - xnots - A desktop sticky notes application for Unix geeks. (new ebuild)
|
Bug#:
214824
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: nelchael@gentoo.org
|
Reported By: gi1242@users.sourceforge.net
|
|
Component: Ebuilds
|
|
|
URL:
http://xnots.sourceforge.net/
|
|
Summary: xnots - A desktop sticky notes application for Unix geeks. (new ebuild)
|
|
Keywords: EBUILD
|
|
Status Whiteboard:
|
|
Opened: 2008-03-26 04:22 0000
|
Hi,
Here's an ebuild for xnots.
xNots is a desktop sticky note system for the X window system and Unix geeks.
xNots is designed so that all your sticky notes and to-do lists are text files
in a certain directory (by default .Pa ~/.xnots). The idea is that any Unix
geek should abhor typing text into anything EXCEPT his favourite editor. These
files completely control the appearance and content of the displayed sticky
notes, and thus the average Unix geek will never have to use the mouse or (god
forbid) navigate using menus to control.
GI
Created an attachment (id=147349) [details]
xnots-0.11.ebuild
There's no such release as 0.2 on SF project page for xnots - only 0.11.
Additionally - I'm attaching fixed ebuild:
* fixed header
* removed useless src_compile
* cleaned up src_install
* fixed mandir
* fixed dependencies
(In reply to comment #2)
> There's no such release as 0.2 on SF project page for xnots - only 0.11.
Oops. I forgot to release it. (I just had the distfile sitting in my
/usr/portage/distfiles). Sorry :).
I also realise that my naming convention (0.11) conflicts with Gentoo's (where
0.2 < 0.11). Accordingly I'm going to nuke 0.11 release, and I just released
0.2.
> Additionally - I'm attaching fixed ebuild:
> * fixed header
> * removed useless src_compile
> * cleaned up src_install
> * fixed mandir
> * fixed dependencies
Thanks for fixing the ebuild. I made a couple of changes before releasing.
Accordingly, a few changes to the ebuild:
1. Added back src_complie, to compile without debugging info.
2. xnots requires inotify support which is not there in kernels before
2.6.13. Accordingly I added >=virtual/linux-sources-2.6.14
I attach both a diff, and the new ebuild.
Thanks,
GI
(In reply to comment #3)
> Thanks for fixing the ebuild. I made a couple of changes before releasing.
> Accordingly, a few changes to the ebuild:
>
> 1. Added back src_complie, to compile without debugging info.
Ok.
> 2. xnots requires inotify support which is not there in kernels before
> 2.6.13. Accordingly I added >=virtual/linux-sources-2.6.14
Depending on kernel sources gives you nothing, as the user can run whatever he
is and have other sources installed. It's better to use elog to give a notice
to users about enabling CONFIG_INOTIFY in kernel.
(In reply to comment #6)
> Depending on kernel sources gives you nothing, as the user can run whatever he
> is and have other sources installed. It's better to use elog to give a notice
> to users about enabling CONFIG_INOTIFY in kernel.
Good point. I updated the ebuild to check for the INOTIFY option. (It was quite
hard to find the eclass that does this, since linux-info.eclass doesn't have a
man page.)
GI
(In reply to comment #7)
> (In reply to comment #6)
> > Depending on kernel sources gives you nothing, as the user can run whatever he
> > is and have other sources installed. It's better to use elog to give a notice
> > to users about enabling CONFIG_INOTIFY in kernel.
>
> Good point. I updated the ebuild to check for the INOTIFY option. (It was quite
> hard to find the eclass that does this, since linux-info.eclass doesn't have a
> man page.)
Dying here on this condition is quite annoying - it's better to use elog to
just inform the user that INOTIFY is required. I've commited xnots-0.2 (no need
for -r1 since it has never been in the tree).
(In reply to comment #9)
> Dying here on this condition is quite annoying - it's better to use elog to
> just inform the user that INOTIFY is required.
OK. Thanks for including it.
Btw -- it might be better to ewarn if the user does not have INOTIFY support,
and be silent otherwise. In case you like that better, I attach a patch.
GI