Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

coinst(1) [debian man page]

COINST(1)						      General Commands Manual							 COINST(1)

NAME
Coinst - computes the co-installability kernel of a package repostory SYNOPSIS
coinst [options] DESCRIPTION
coinst reads a package repository in debian format or RPM format from standard input, and computes the co-installability kernel of the repository (see below). The graph of the kernel is written in dot format to a file, and a diagnostic is written to standard output. This diagnostic consists by default of: - the list of equivalence classes of packages - the list of non-installable packages - the list of not co-installable pairs of packages CO-INSTALLABILITY KERNELS A set of packages is called co-installable with respect to a repository R if it can be extended to a set of packages from R that satisfies all inter-package relations (dependencies, conflicts, etc.). In particular, a package p is installable if the set {p} consisting of p only is co-installable. This tool reduces a repository R to a much smaller one, its so-called co-installability kernel R', that behaves exactly the same as far as co-installability of package is concerned: Any set of packages P is co-installable with respect to P iff it co-installable with respect to R'. This is achieved by - dropping all relations that are not relevant for this purpose. For instance, dependencies that do not lead directly or indirectly to any conflicts are dropped. - identifying all packages that behave the same. For instance, packages that are not in conflict with any other package (even not through dependency chains) behave the same since they are co-installable together with any other co-installable set of packages, and packages that are not installable at all behave the same since they may never be part of any co-installable set of packages. A more precise explanation can be found in the original research article underlying this tool. The interest of computing the kernel is that it is typically orders of magnitude smaller than the original repository. OPTIONS
Options controlling the input -deb expect input in the format of a debian Packages file (default). -rpm expect input in the format of an RPM hdlist.cz file. -ignore package ignore the package named package. Options controlling the graph output -o file write the graph to file instead of graph.dot -all include all packages in the coinstallability graph -root p draw only the relevant portion of the graph around package p. Options controlling the diagnostic output -explain explain the list of non-installable pairs of packages. -stats show statistics regarding the input and output repositories Miscellaneous options -help, --help show command synopsis EXAMPLE
Reduce a current debian Packages file to its kernel: coinst -all -o raw.dot < sid_main_binary-amd64_Packages Layout the graph: dot raw.dot -o layout.dot: View the graph with dotty, or the viewer from the coinst_viewer package: dotty layout.dot coinst_viewer layout.dot AUTHOR
Coinst has been written by Jerome Vouillon. This manpage has been compiled by Ralf Treinen from the original coinst documentation. SEE ALSO
dot(1),dotty(1),coinst_viewer(1) http://coinst.irill.org The original research article decribing the algorithm behind this tool is Roberto Di Cosmo and Jerome Vouillon, On software component co- installability, 19th ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE-19) and ESEC'11: 13rd European Software Engi- neering Conference (ESEC-13), Szeged, Hungary, September 5-9, 2011, pages 256-266. COINST(1)

Check Out this Related Man Page

EDOS-BUILDDEBCHECK(1)					      General Commands Manual					     EDOS-BUILDDEBCHECK(1)

NAME
Edos-builddebcheck - Check satisfiability of Debian package build-dependencies SYNOPSIS
edos-builddebcheck [option] ... Packagefile Sourcepackagefile DESCRIPTION
edos-builddebcheck reads a set of Debian package descriptions from the file Packagefile, each of which is in the format of deb-control(5), and a set of source package descriptions from the file Sourcepackagefile. All packages described in the file Packagefile must have the same value of their Architecture (if it is different from all). For instance, the Packages and Sources files as found on a Debian mirror server, or in the directory /var/lib/apt/lists/ of a Debian sys- tem, are suitable as input files. edos-builddebcheck verifies for every of the source packages (from Sourcepackagefile) whether its build-dependencies, build-indep-dependen- cies and build-conflicts can be satisfied from the binary packages provided in Packagefile. Only build-relations that apply to the archi- tecture (see below on how the architecture is determined) are taken into account. Note that this is not the same thing as checking whether a distribution can be rebuild from scratch, for several reasons: 1. No actual compilation is taking place, this tool only does a static analysis of package relationships. 2. The binary packages in Packages are not necessarily those that are the result of the compilation of the source packages in Sourcepack- agefile. 3. We do not check for cycles. For instance, suppose that we have source packages a and b both generating one binary package of respec- tively the same name, and that a build-depends on b and b build-depends on a. Then we can not rebuild the set of packages from scratch because of the cycle. However, if we already have binary packages a and b then we can recompile both of them. Consequently, edos-buildde- bcheck will not report an error in this case. 4. The underlying logical machine does a complete analysis of alternatives, and might report satisfiability of constraints in case actual tools (like apt) fail to find a solution. Build-essential packages are ignored in unversioned build-dependencies. The (architecture dependant) list of build-essential packages is read from the configuration file. If that file is not available than an architecture independent default value is used. OPTIONS
-a, --architecture architecture Check for compilation on architecture. Usually it is not necessary to specify the architecture since it can be derived from the Packages file. -be, --binexplain Add all explanations why build-dependencies are not satisfiable. Without that option some of these explanations may be missing from the output in case a source package build-depends on a binary package that exists in Packagefile file but that edos-debchecks finds not to be installable inside Packagefile. FILES
/etc/edos-builddebcheck.conf Configuration file for edos-builddebcheck AUTHOR
Edos-builddebcheck has been written by Stefano Zacchiroli <zack@debian.org> and Ralf Treinen <treinen@debian.org>. It heavily relies on edos-debcheck which has been written by Jerome Vouillon for the EDOS project. SEE ALSO
deb-control(5),edos-debcheck(1) EDOS
2010-04-22 EDOS-BUILDDEBCHECK(1)
Man Page