On Mon, Feb 18, 2002 at 09:53:45AM -0400, Ben Armstrong wrote:
> Debian source package trees (again, either native or non-native) can build &
> install by "make all && make install" provided the Debian maintainer has not
> "tainted" the Makefiles with code that will only give sensible results when
On Tue, Feb 19, 2002 at 12:22:42AM +0500, Victor Porton wrote:
> Well, what about these native packages?
They only differ in the form of the source package, not the mechanism by
which they are built.
> Do, I understand correctly that for native packages the installation
> directories are 'fictiv
On Mon, Feb 18, 2002 at 09:53:45AM -0400, Ben Armstrong wrote:
> Debian source package trees (again, either native or non-native) can build &
> install by "make all && make install" provided the Debian maintainer has not
> "tainted" the Makefiles with code that will only give sensible results when
On Tue, Feb 19, 2002 at 12:22:42AM +0500, Victor Porton wrote:
> Well, what about these native packages?
They only differ in the form of the source package, not the mechanism by
which they are built.
> Do, I understand correctly that for native packages the installation
> directories are 'ficti
On Tue, Feb 19, 2002 at 12:22:42AM +0500, Victor Porton wrote:
> Well, what about these native packages?
Well, they are totally normal in every respect. Only they already have
all the information (i.e. a full uptodate debian/-dir) needed to build
them without a Debian specific patch.
It's general
> Not quite. Source packages typically consist of an original tarball, a
> .diff, and a .dsc (unless it is a native package, which doesn't have
> a .diff).
Well, what about these native packages?
Do, I understand correctly that for native packages the installation
directories are 'fictive' (to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig, could you please describe more fully what you want to do? Are
you trying to take a precompiled program (like distributed-net) and
package it for use or are you compiling the program and only want
binary packages available?
- --
Warren
GPG F
On Sun, Feb 17, 2002 at 09:21:11AM -0500, Craig wrote:
> Here's what i'm trying to do:
>
> * Create a .DEB that contains only 2 simple binaries, plus a couple of
> dependencies. (i'll have another package, tar ball for right now, for the
> source code).
Is this for your personal use, or is it
On Tue, Feb 19, 2002 at 12:22:42AM +0500, Victor Porton wrote:
> Well, what about these native packages?
Well, they are totally normal in every respect. Only they already have
all the information (i.e. a full uptodate debian/-dir) needed to build
them without a Debian specific patch.
It's genera
> Not quite. Source packages typically consist of an original tarball, a
> .diff, and a .dsc (unless it is a native package, which doesn't have
> a .diff).
Well, what about these native packages?
Do, I understand correctly that for native packages the installation
directories are 'fictive' (to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig, could you please describe more fully what you want to do? Are
you trying to take a precompiled program (like distributed-net) and
package it for use or are you compiling the program and only want
binary packages available?
- --
Warren
GPG
On Sun, Feb 17, 2002 at 09:21:11AM -0500, Craig wrote:
> Here's what i'm trying to do:
>
> * Create a .DEB that contains only 2 simple binaries, plus a couple of
> dependencies. (i'll have another package, tar ball for right now, for the
> source code).
Is this for your personal use, or is i
On Sun, Feb 17, 2002 at 09:21:11AM -0500, Craig wrote:
>
> Hi all,
> Here's what i'm trying to do:
>
> * Create a .DEB that contains only 2 simple binaries, plus a couple of
> dependencies. (i'll have another package, tar ball for right now, for the
> source code).
Deb packages contain binari
On Sun, Feb 17, 2002 at 09:21:11AM -0500, Craig wrote:
>
> Hi all,
> Here's what i'm trying to do:
>
> * Create a .DEB that contains only 2 simple binaries, plus a couple of
> dependencies. (i'll have another package, tar ball for right now, for the
> source code).
Deb packages contain binar
Hi all,
Here's what i'm trying to do:
* Create a .DEB that contains only 2 simple binaries, plus a couple of
dependencies. (i'll have another package, tar ball for right now, for the
source code).
Can that be done? You don't *REQUIRE* the source code to be in the .deb, do
you? Or is that ho
Hi all,
Here's what i'm trying to do:
* Create a .DEB that contains only 2 simple binaries, plus a couple of
dependencies. (i'll have another package, tar ball for right now, for the
source code).
Can that be done? You don't *REQUIRE* the source code to be in the .deb, do
you? Or is that h
16 matches
Mail list logo
