Re: make command understanding
On Thu, 2013-01-31 at 13:29 +0100, berenger.morel@neutralite.org wrote:
> _ easier to remove
No, self compiled is as easy to remove as a package
> _ easier to maintain
No, simply build a package
> _ tried by other (at least, by people who made them)
Correct, they are tested by the community, the people who build the
packages often don't test their packages
> _ they can be signed
If you build the packages yourself, than there is no need to sign it,
but if you like, than sign your own packages
> _ less dependencies (no need to install all *-dev packages of their
> dependencies, and their own dependencies, same for makefile
The dependencies for the build package or directly installed software
are the same, just for compiling you need headers. It's a bad habit of
Debian to separate software into app, libs and headers and often it does
cause serious issues, just take a look at the jack devel mailing list
archive. People don't care about bloated DEs, but they care about some
bytes to have everything linked correctly, by one package, two policies
that don't fit together.
> generators:
> someone has spoken about ./configure, but there is also cmake, qmake,
> scons, and many other)
such as ./waf
Reply to: