Manoj Srivastava wrote:
Hi,
Aaron Close, but not quite. I would like 'make install' or similar
Aaron to build the programs, configuration files, pre/postinst
Aaron scripts, and then install them, _without_ actually building a
Aaron .deb binary package file, but still modifying dpkg's view of
Aaron Denney writes:
I would like 'make install' or similar to build the programs,
configuration files, pre/postinst scripts, and then install them,
_without_ actually building a .deb binary package file, but still
modifying dpkg's view of what is installed.
This would seem to require either
Manoj Srivastava writes:
Then the solution is to write a simple script:
==
#! /bin/sh
./debian/rules binary
dpkg -i ../*.deb
==
Even this
Looking through the available documentation, it seems that the only way
to install source package is to use it to create a binary package, and
then install the newly created binary package. Am I missing something or
is this the only way? If this is the only way, why is this necessary?
I would
-BEGIN PGP SIGNED MESSAGE-
Aaron Denney:
Looking through the available documentation, it seems that the only way
to install source package
This is a contradiction. source packages are not installed.
is to use it to create a binary package, and
then install the newly created binary
Santiago Vila Doncel writes:
That extra step does often take just a little more time. The build takes
often much more time. *.deb files have an internal structure that only
dpkg knows about. I'm not sure what you want to achieve.
I thought he was fairly clear. He wants 'make install' to
Hi,
john == john [EMAIL PROTECTED] writes:
john Santiago Vila Doncel writes:
That extra step does often take just a little more time. The build
takes often much more time. *.deb files have an internal structure
that only dpkg knows about. I'm not sure what you want to achieve.
john I thought
In article [EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
Santiago Vila Doncel writes:
That extra step does often take just a little more time. The build takes
often much more time. *.deb files have an internal structure that only
dpkg knows about. I'm not sure what you want to achieve.
I
On 12 Nov, Aaron Denney let loose with:
In article [EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
Santiago Vila Doncel writes:
That extra step does often take just a little more time. The build takes
often much more time. *.deb files have an internal structure that only
dpkg knows about. I'm
Hi,
Aaron == Aaron Denney [EMAIL PROTECTED] writes:
Aaron Close, but not quite. I would like 'make install' or similar
Aaron to build the programs, configuration files, pre/postinst
Aaron scripts, and then install them, _without_ actually building a
Aaron .deb binary package file, but still
10 matches
Mail list logo
