Use of /usr/local: maybe I'm old school but when possible I think /usr/local should be left for the person running the machine to use. Things from package management systems should go somewhere else. Others will disagree with me about this I expect.
Heh, I think you'll be surprised at what you'll find in your /usr/local directory. In my case, so far, everything that's installed into /usr/local has been from 3rd party packages. So in keeping with "tradition" I will leave it as-is for now
Tradition is that /usr/local is for the system admin typing on the keyboard, not for packages managed by package management systems. There is *nothing* in /usr/local on my system except what I have put there. Perhaps your rom preference deals with this differently, I don't know.
I do know that /usr/local is where I am supposed to install things the old fashioned way. The ipkg system has no knowledge about what the local admin installs there and will eventually step on things.
Location of jwhois.conf: If jwhois looks for its conf file in /usr/local/etc/ then there will be problems if someone installs this package in an unusual place.
Correct me if I'm wrong, but I thought all the symlinking business takes care of this?
On a 6000 with a stock sharp rom nothing does this by magic. Again your rom may deal with it differently. You can easily test by installing it to a different place to see what happens.
If this is GPL software I believe you are required to distribute the license file(s) along with the binary package. I think tossing them into the CONTROL directory is fine for this purpose.
Good idea, done. Although along with the license line in the control file, 99% of the people using IPKs will not know it's there and will not have a chance to read it before ipkg-install deletes it
ipkg shouldn't delete it until the package is removed, but it will be hidden away with the install scripts.
John