Help - Search - Members - Calendar
Full Version: Jwhois 3.2.3
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
desertrat
OK here's my first attempt at compiling and making an ipkg for pdaXrom smile.gif

jwhois 3.2.3 (http://www.gnu.org/software/jwhois/jwhois.html)

I would be grateful if an "oldhand" would check it over to see whether I have made any mistakes (and let me know before I pick up some bad habits!)

-- cheers

[attachment updated: now installs to "/" instead of /usr/local, also corrected permissions]
inode0
QUOTE(desertrat @ Jan 12 2006, 07:13 PM)
OK here's my first attempt at compiling and making an ipkg for pdaXrom smile.gif

jwhois 3.2.3 (http://www.gnu.org/software/jwhois/jwhois.html)

I would be grateful if an "oldhand" would check it over to see whether I have made any mistakes (and let me know before I pick up some bad habits!)

-- cheers
*

Here are a few thoughts in general.

control: I find it nice if you include a License line in here indicating the controlling license for the software.

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.

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. I would add a postinst script to check for the install root and create a link from /usr/local/etc/jwhois.conf to wherever it was really installed. Then a postrm script can remove that link if it was created at install.

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.

John
desertrat
Thanks for the comments.

QUOTE(inode0 @ Jan 12 2006, 07:43 PM)
Here are a few thoughts in general.

control: I find it nice if you include a License line in here indicating the controlling license for the software.


Done.

QUOTE
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 smile.gif

QUOTE
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?

QUOTE
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 smile.gif

-- cheers
inode0
QUOTE(desertrat @ Jan 12 2006, 08:35 PM)
QUOTE
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 smile.gif


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.

QUOTE(desertrat @ Jan 12 2006, 08:35 PM)
QUOTE
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.

QUOTE(desertrat @ Jan 12 2006, 08:35 PM)
QUOTE
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 smile.gif


ipkg shouldn't delete it until the package is removed, but it will be hidden away with the install scripts.

John
iamasmith
QUOTE(desertrat)
QUOTE(inode0)
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 smile.gif


There is a good reason that /usr/local isn't used for stuff that's distribution compiled and that is it doesn't get confused with what you built that doesn't come from the distribution package management system.

For example if you use Gentoo linux you will use emerge to build everything from source, if you use redhat you will use the RedHat network, if you use SuSE you will use Yast etc. etc.

Anything that you install yourself will be unmanaged by the distribution stuff.

Since you are have produced an ipk that is handled by ipkg (the pdaXrom package management system) then I think inode0 truly has the higher ground here.

Basically, /usr/local should be left for folk to tinker with and delete if necessary with the certainty that they will only undo their own work.

btw: Thanks for bringing that to our attention here inode0 it is a good practice to continue.

- Andy
pgas
QUOTE
correct me if I'm wrong, but I thought all the symlinking business takes care of this?


on pdaxrom links are created during install

QUOTE
Tradition is that /usr/local is for the system admin typing on the keyboard

desertrat was talking about the other user contributed ipks for pdaxrom, hence the quote for "tradition".

QUOTE
it is a good practice to continue.


Maybe we could had --prefix=/usr in the list of options to pass in the howto....

If someone want to update the howtos on http://mail.pdaxrom.org/contrib/
feel free to do it and send me the updated version.

I've mirrored jwhois on http://mail.pdaxrom.org/contrib
desertrat
QUOTE(inode0 @ Jan 12 2006, 08:48 PM)
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.


OK updated to use "/" (or rather, not use /usr/local).

QUOTE
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.


I think you're in the wrong forum laugh.gif , this is for pdaXrom!

QUOTE
ipkg shouldn't delete it until the package is removed, but it will be hidden away with the install scripts.

Yep, you're right it hides it in "<prefix>/usr/lib/ipkg/info/".

-- cheers
desertrat
QUOTE(pgas @ Jan 13 2006, 08:07 AM)
QUOTE
Tradition is that /usr/local is for the system admin typing on the keyboard

desertrat was talking about the other user contributed ipks for pdaxrom, hence the quote for "tradition".

Bingo smile.gif

QUOTE
Maybe we could had --prefix=/usr in the list of options to pass in the howto....

If someone want to update the howtos on http://mail.pdaxrom.org/contrib/
feel free to do it and send me the updated version.

I have a modified version which corrects some typos. I've also added a few words about not locating ipkg-tmp on a fat/vfat/messydos partition (as this messes up the permissions). I will email this to you.

QUOTE
I've mirrored jwhois on http://mail.pdaxrom.org/contrib

Sorry please mirror again, as I have changed the package (corrected permissions and now does not use /usr/local).
pgas
QUOTE
I have a modified version which corrects some typos. I've also added a few words about not locating ipkg-tmp on a fat/vfat/messydos partition (as this messes up the permissions). I will email this to you.

Great!

QUOTE
Sorry please mirror again, as I have changed the package (corrected permissions and now does not use /usr/local).


np, done.
inode0
QUOTE(desertrat @ Jan 13 2006, 08:39 PM)
QUOTE
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.


I think you're in the wrong forum laugh.gif , this is for pdaXrom!

I got lost there for a minute. I'll be heading back to where I belong soon. Have fun guys.

John
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2015 Invision Power Services, Inc.