changing "make package" destination name

[John Refling]

I have created a package makefile which checks if
X is installed and builds the package one way if
it isn't installed, and builds it another way (eg
a few extra binaries) if X is installed.

Problem is if you "make package" to make the binary
packages in the two different cases, we will get
two slightly different binary packages, but with the
same name.

Is there a way to change the name so one is something
like yyy-without-x11 and the other is yyy-with-x11?

Is this whole thing problematic, and should I just
have two slightly different packages, named as above?

[Frederick Bruckman]

On Tue, 28 Mar 2000, John Refling wrote:

> I have created a package makefile which checks if
> X is installed and builds the package one way if
> it isn't installed, and builds it another way (eg
> a few extra binaries) if X is installed.

The body of precedent stands behind making two packages, with the
"xpackage" depending on the plain "package" and installing only the
extra stuff. Ideally, the "X" package would only extract and build the
required bits, but there are a few nasty packages that re-build an
entire distribution, only to install part of it, if you must do that
(coda5-{client,server} comes to mind).

[David Brownlee]

Generally two different packages is best - in some cases having
the -x11 package depend on the other can be good.

David/absolute

On Tue, 28 Mar 2000, John Refling wrote:

> I have created a package makefile which checks if
> X is installed and builds the package one way if
> it isn't installed, and builds it another way (eg
> a few extra binaries) if X is installed.
>

[Greg A. Woods]

[ On Wednesday, March 29, 2000 at 01:13:17 (+0100), David Brownlee wrote: ]
> Subject: Re: changing "make package" destination name

>
> Generally two different packages is best - in some cases having
> the -x11 package depend on the other can be good.

Except in rare cases where the package's binaries are statically linked,
or where the x11 (or whatever optional) component is highly optional at
runtime, etc., it is vitally important that there be separate packages
in order to properly support binary packaging.

--
Greg A. Woods

+1 416 218-0098 VE3TCP <gwo...@acm.org> <robohack!woods>
Planix, Inc. <wo...@planix.com>; Secrets of the Weird <wo...@weird.com>