Re: apt-get source
On Wed, 18 Jan 2006 16:05:43 +0200
David Baron <d_baron@012.net.il> wrote:
> Having failed to get apt-build to work, I tried this. I can easily compile and
> install stuff that the kde packages will not due to dependency problems
> (around qt3 and kde) and I get the Debian version (versions posted on
> kde-apps, sourceforge had unrelated compilation problems!).
>
> A few kudos here:
>
> 1. The sources are expanded into the home/user's directory. /usr/src might be
> a better choice but this is OK, however
The source goes where you are when you do the apt-get.
> 2. The permissions are set to a strange mix of root (apt-get must be run as
> root) and some default user, in my case "knoppix" (forgive me Debian, I have
> sinned). So before proceding, a chown -R to me:me :-)
Has not seemed to be a problem as far as I can tell on my machine.
> 3. If I simply compile and install, the thing goes to /usr/bin. This is very
> undesirable since this install is not "registered" in apt. The configure
> prefix must be set to /usr/local or /opt or anything other than /usr.
It is intended to be built with dpkg-buildpackage from the top level of
the source directory, in which case you will be informed if any build
dependencies are missing. If the expected versions of packages don't
match your system you either have to correct that or correct the stuff
in the source/debian directory. In many cases this could be as simple as
changing all instances of conflicting version information in the
control file.
> Now, a recent post taked about dpkg-repack'ing such an installation. Would
> this make a deb out of this installation that would work canonically? (In
> this case, I would leave the prefix to its /usr default.)
The way dpkg-repack works is it uses information about the
installed package from /var/lib/dpkg/info/ to make a new .deb file,
information that doesn't exist for things not installed through the
packaging system, hence the repack and not pack.
You can use check-install to create a .deb package from source you
compile, but there will not be any dependency information/resolution.
It's good when used sparingly, but try not to get too carried away with
big groups or too many layers of packages.
Later, Seeker
Reply to: