I have build a package from source , unfortunately I did not pay attention and the build application (checkinnstall) build the package as default version of 2.0-1.

It would fit better into the project if I could change the version #.
I have not found how, I can only read the current parameters of the package.

Any idea how to do that?

You don't mention your distro, but, generally speaking, since you installed it from sources, your package manager will not have it in its list for updating.

My guess is that your best bet is to find remove (you can do that from the build directory by issuing the command make uninstall as root), the find the sources for the newer version and compile the newer version.

Thanks,
I'll think I better rerun the package build and set the version to match the main project.

if you are building from source, you have 2 avenues, one already mentioned, the other is to convert it to the package type of your distro. Most distos have put in place a method to do this. you'll have to look in to that part of it. Still if it is not provided by the repos. it is a rinse and repeat situation.

I am not sure that would help since the checkinstall already build "Debian" package.
But I have already rerun the build and now chasing dependencies. Fun never stops.

yep keeps one busy. I use a home made build script to automate the building and installing the deps first then the main app last.

But I use Slackware. They Incorporated the ./configure , make , make install into there package system. that makes it a lot easier when making a package. VOID Linux, I just run my slackuilds I've modded on it, if what I am looking for is not in the repo. which is a not much situation in that arena on void as well. maybe like one or two things for that.

You could create a script the pulls the latest source for each one ( wget ) then checks version, untar, configure, make and make install in order to make it a little easier for you.

You'd still have to set up a method to uninstall the older versions first, but I think you love a good challenge.

Or switch to Slackware, where that'd be a cinch to do then say debian.

I was really not ready to "back-paddle" from the task.
SO I am taking the easy ways to do that and not ready to spent time to "automate" this process.

After all this is done I like to really dig into "make" and associated "automation".
I have been avoiding learning "make" for few years now, but I really need to bite the bullet.


I found this "chekinstall" and it initially worked on my first "configure / make /make install".
But as I said - I did not pay much attention to options, but I think it has "dependencies" option which I need now.
The "problem" is I still have to run "configure" and then run "checkistall" before I can option it - obviously.

I find it frustrating to learn that each distro have its own ways to accomplish stuff.
Not sure if that is the best way to advance art of programming.
For example the original "bluez" package is not officially on github and what is there is older version of it.

Speaking of version , I need to post my latest hitch.
Later...

https://debian-administration.org/ar...h_checkinstall

that looks like a nice piece of software, it wasn't around, or I had no idea of its existence a few years back when I tasked myself to creating deb's for a project of mine.

being the aftermath of running configure. still it cuts making a deb down to what, two commands?
that's a lot sweeter then what I remember having to go through.