Suppose I have an installer program or source tarball for some program I want to install. (There is no Debian package available.) First I want to create a .deb package out of it, in order to be able to cleanly remove the installed program in the future (see Uninstalling application built from source, If I build a package from source how can I uninstall or remove completely?).
I have always had a problem installing and removing compiled software, so I have decided I would like to build software from source into a .deb package for easier installation/removal.
I would like to know of an easy and short way to build source into a .deb package, as an end user.
I have tried:
ubucompilator, which did not work for me
This how to guide, but I found it too long
I'm trying to build a package on Launchpad's Debian build system for PPAs but I'm having some issues with a certain package.
The package I'm trying to build (zorin-xwinwrap) contains a source C file which I'm trying to get to compile and build on Launchpad's server so that it would install and work on 32 bit (i386) and 64 bit (amd64) systems.
chamber wrote:man pacman wrote: -Q, --query Query the package database. This operation allows you to view installed packages and their files, as well as meta-information about individual packages (dependencies, conflicts, install date, build date, size).
I've read elsewhere that to uninstall a package you built using './configure && make' etc. you have to read the Makefile to determine where on the system files may have been placed. Only, I can't read this out of the makefile due to inexperience.
The package I'm trying to uninstall is called 'movgrab'.
Ok, here is one thing that puzzles me... I'm trying to build a package from source, and then use checkinstall to generate a .deb package.
Is there an application by which the build dependency as well as the source code of the software gets downloaded automatically as soon as we install the software from a .deb package or the software center?
We are switching over to using puppet for configuration management of our Linux based systems. We have several 3rd party packages which contain custom binary installers (think JDK) and are using RPM to build them into local-only non-distributed packages.
I got from one guy a directory with bunch of zip files (/binary/*), and a pckg_list file, with a structure like, for example, that:
Package : TIZEN-IDE
Version : 1.0.0
OS : windows
Build-host-os : linux
Maintainer : JongHwan Park <jonghwan2.park@samsung.com>
Attribute : meta
Install-dependency : assignmenttracing-eplugin, sdb, eventinjector-eplugin, telephony-eplugin, webapp-eplugin, docume