Hello. dbskkd-cdb is a fast, reliable dictionary server for the SKK Japanese-input software. It works under inetd so that you can restrict accesss to the server with tcp-wrappers. I suggest dev-db/freecdb and app-i18n/skk-jisyo-cdb as this version of dbskkd-cdb cannot be compiled with the current version (0.75) of dev-db/cdb.
Created attachment 11499 [details] dbskkd-cdb-1.01.ebuild
Created attachment 11500 [details] dbskkd-cdb.xinetd
It depends on dev-db/freecdb while building. The portage version (0.75) of dev-db/cdb is not compatible with the submitted version (1.01) of dbskkd-cdb.
dbskkd-cdb depends on app-i18n/skk-jisyo-cdb when it runs.
Taking this one - Masatomo, I think this would have been assigned to you but I currently have a bit spare time.
Ooops, forgot that click...
Done - but please be sure to check the license next time. This looks more like "as-is" than like GPL.
Thanks! Yeah, I noticed that it looks like as-is when you take a look at LICENSE file; but at the end of its Release-Notes it says: > Redistribution of this software > > Redistribution of this software is under the GNU Public License. > For the further details, consult to each file of the package. so I thought dbskkd-cdb is under GPL. (Red Hat also treats it as GPL'd software) Surely it is a little bit confusing and I'll check it out next time.
I think it should be RDEPEND to 'sys-apps/xinetd' or include inetd.conf line. What do you think?
I just emailed the author because of the license... it is not clear which applies. About (x)inetd: I will have a look how other packages handle this.
Created attachment 11553 [details] dbskkd-cdb.xinetd (fixed typo) Sorry I included wrong xinetd conf file. "server skkserv" should be "service skkserv".
There are few packages that depend on virtual/inetd (only net-ftp/ftpd and net-mail/qpopper at the point) and both of them do not include inetd.conf file. Qpopper's ebuild, however, puts a messege about inetd.conf in pkg_postinst() section. Personally I uses inetd to invoke dbskkd-cdb server so I don't want it to depend on xinetd. Qpopper's solution (show some notice about inetd.conf) would be better than doing nothing, but probably the best way is to include inetd.conf as you mentioned.
Now it checks for /usr/sbin/xinetd and creates an example configuration line for inetd in /etc/inetd.skkserv (and gives some notice) if it does not find it. Ok?
Thanks. The ebuild file has been improved so much :-)