Comments on: HOWTO: Compiling packages from source on Debian Linux

By: Admin

Admin — Mon, 15 Feb 2010 17:57:04 +0000

I think Ryan is trying to tell that if you don’t change the version of the package, next time when you do an apt-get update/upgrade it will try to overwrite your custom compiled package and hence your changes will get lost. So by changing the version, apt-get won’t interfere with your custom deb package.

By: phr3ak

phr3ak — Sun, 14 Feb 2010 10:36:00 +0000

Do you understand my question?

By: phr3ak

phr3ak — Tue, 27 Oct 2009 10:48:58 +0000

why want upgrade if the version of installed package is same as stock package? where is the difference between local compiled package and stock package?

By: Admin

Admin — Tue, 27 Oct 2009 05:14:59 +0000

What do you not understand exactly?

By: phr3ak

phr3ak — Wed, 21 Oct 2009 07:49:06 +0000

but i don’t understand well. could you explain, please?

By: Ryan

Ryan — Tue, 20 Oct 2009 23:49:10 +0000

Please read my previous comment. I addressed exactly this problem.

By: phr3ak

phr3ak — Tue, 20 Oct 2009 22:35:40 +0000

Anyone knows debian why want upgrade the compiled package if that is same version like in repository?

By: Admin

Admin — Thu, 24 Sep 2009 05:39:16 +0000

Hi Ryan,

You are right. debuild is a wrapper function.

Thanks for the versioning tip. I just wanted to post something by which anyone can quickly compile packages. Certainly if those packages are going to be used by a lot of people, then yes, one should do it in a more *correct* manner.

By: Ryan

Ryan — Tue, 22 Sep 2009 19:53:02 +0000

What about debuild? It’s what I’ve been using, and from the manpage, it seems to be a wrapper for dpkg-buildpackage along with some other tools.

Also, if you are compiling the same version as the one from the repositories, Debian will try to “upgrade” to the binary package from the server, which is not what you want. To fix this, use to bump the version of the source package in a portable way. Just run debchange –nmu and then enter a description of what you changed.

By: Alan

Alan — Mon, 06 Jul 2009 04:22:59 +0000

Thanks for documenting this. I usually end up compiling packages from source for two reasons:

1. Bandwidth is expensive where I live (so I want to reuse the source if I switch from Debian to Slackware or whatever, instead of getting only a .deb).

2. Debian’s usually a few versions behind

This works well for packages which aren’t integrated too much into the core of the system, otherwise you get into dependency hell and it gets ugly.

Also, this requires knowledge of the ./configure, make, make install process! Deb sources is a good way for beginners to learn, though!

Thanks again! Long live Debian!

Alan

By: Compiling packages from source on Debian Linux | Debian-News.net - Your one stop for news about Debian

Sun, 05 Jul 2009 22:17:36 +0000

[...] In this post we will learn how to build a Debian package (.deb) from source packages. You might be thinking why would I ever need to do that, right? Well most of the times you are right, you won’t require to build packages from source, but there will be situations sometimes when you will be required to do this. More here [...]