Building dep package for 64bit ubuntu 10.10

jmc1987 · 02-23-2011, 06:29 PM

I am trying to build a deb package and I am lost. I was trying to follow this tutorial http://ubuntuforums.org/showthread.php?t=51003 and I am not sure what kinda of package this should be.

Can somebody point me in the right directions im really lost on this.

The driver is http://sourceforge.net/projects/cupsdriverkodak/files/ file c2esp16.tar.gz

Thanks

tredegar · 02-24-2011, 11:32 AM

On the sourceforge page you linked to there is a README file.
It says to read the INSTALL file, still on that page.

I read it.

It has clear instructions for installing this driver.

There are notes specific to ubuntu and debian.

It says nothing about A 64-bit kernel. This might matter, but there's only one way to find out.....

If you are using ubuntu > 9.10, when you get to the bit about restarting cups, the command has changed and is now sudo service cups restart

If you get stuck, please get back to us with what isn't working for you.

I hope you realise you do not need to create a deb package if all you want to do is compile and install the driver (and instructions for this are in the INSTALL file).

Hope this helps.

jmc1987 · 02-24-2011, 12:06 PM

Yes I've read the readme and it works fine like that. But I want to put it into a debian package so I can keep track of installed software. I did run it in vbox and printed with it over the network so I know it does work with 64bit ubuntu. Just tring to put it into a .deb is a toughy for me. I don't want to end up with a bunch of compiled software installed and lose track of it. They offer a 32bit deb but I need 64 lol. But I'll still continue to research when I get time.

tredegar · 02-24-2011, 01:18 PM

I don't see how making a deb is going to help you "keep track of installed software".

For every install I keep a file InstallNotes_DistroName-Version. In that I document "X did not work, this link .... helped. Bottom line = Get the firmware file xxx.yyy.bin and put it in /usr/lib/whatever/firmware". I just keep appending notes to that file. it is a useful reference as I maintain quite a few PCs for family & friends.

By the time the next distro / release comes along, the old problems are usually solved (so my notes are only occasionally useful - eg if I need to do a reinstall, or for solving problems here on LQ), and completely new ones arise.

Good luck.

jmc1987 · 02-24-2011, 01:41 PM

Quote:

Originally Posted by tredegar

I don't see how making a deb is going to help you "keep track of installed software".

For every install I keep a file InstallNotes_DistroName-Version. In that I document "X did not work, this link .... helped. Bottom line = Get the firmware file xxx.yyy.bin and put it in /usr/lib/whatever/firmware". I just keep appending notes to that file. it is a useful reference as I maintain quite a few PCs for family & friends.

By the time the next distro / release comes along, the old problems are usually solved (so my notes are only occasionally useful - eg if I need to do a reinstall, or for solving problems here on LQ), and completely new ones arise.

Good luck.

Well I prefer keeping software only install by the package manager. This is also recommend by lots of linux gurus as well. So thats my goal to do it as well.