Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 214824
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Krzysiek Pawlik <nelchael@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Gautam Iyer <gi1242@users.sourceforge.net>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
xnots-0.2.ebuild Ebuild for xnots-0.2 (new) text/plain Gautam Iyer 2008-03-26 04:23 0000 568 bytes Details
xnots-0.11.ebuild xnots-0.11.ebuild text/plain Krzysiek Pawlik 2008-03-26 09:08 0000 520 bytes Details
xnots-0.2-r1.ebuild.patch Diff to the new ebuild (0.2-r1) patch Gautam Iyer 2008-03-26 20:07 0000 437 bytes Details | Diff
xnots-0.2-r1.ebuild Ebuild for xnots-0.2-r1 text/plain Gautam Iyer 2008-03-26 20:08 0000 596 bytes Details
xnots-0.2-r1.ebuild Ebuild for xnots-0.2-r1 (Added INOTIFY kernel option check) text/plain Gautam Iyer 2008-04-06 02:56 0000 690 bytes Details
xnots-0.2-r1.ebuild-warn-inotify Patch to only warn user if he doesn't have INOTIFY support patch Gautam Iyer 2008-04-12 01:28 0000 916 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 214824 depends on: Show dependency tree
Bug 214824 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   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

------- Comment #1 From Gautam Iyer 2008-03-26 04:23:51 0000 -------
Created an attachment (id=147334) [details]
Ebuild for xnots-0.2 (new)

------- Comment #2 From Krzysiek Pawlik 2008-03-26 09:08:35 0000 -------
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

------- Comment #3 From Gautam Iyer 2008-03-26 20:06:37 0000 -------
(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

------- Comment #4 From Gautam Iyer 2008-03-26 20:07:44 0000 -------
Created an attachment (id=147400) [details]
Diff to the new ebuild (0.2-r1)

------- Comment #5 From Gautam Iyer 2008-03-26 20:08:38 0000 -------
Created an attachment (id=147402) [details]
Ebuild for xnots-0.2-r1

------- Comment #6 From Krzysiek Pawlik 2008-04-05 15:33:03 0000 -------
(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.

------- Comment #7 From Gautam Iyer 2008-04-06 02:54:52 0000 -------
(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

------- Comment #8 From Gautam Iyer 2008-04-06 02:56:11 0000 -------
Created an attachment (id=148810) [details]
Ebuild for xnots-0.2-r1 (Added INOTIFY kernel option check)

------- Comment #9 From Krzysiek Pawlik 2008-04-10 08:57:09 0000 -------
(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).

------- Comment #10 From Gautam Iyer 2008-04-12 01:26:28 0000 -------
(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

------- Comment #11 From Gautam Iyer 2008-04-12 01:28:31 0000 -------
Created an attachment (id=149455) [details]
Patch to only warn user if he doesn't have INOTIFY support

The diff is against xnots-0.2.ebuild in the current portage tree.

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug