We currently use postfix as a part of our overall product, which means that
it ends up being packaged inside our own RPM (or deb, etc) packages, and
then redeployed when our product is installed. One thing I've noticed
about the postfix build system in this is that it assumes you are building
Quanah Gibson-Mount:
We currently use postfix as a part of our overall product, which means that
it ends up being packaged inside our own RPM (or deb, etc) packages, and
then redeployed when our product is installed. One thing I've noticed
about the postfix build system in this is that it
On Mon, Feb 09, 2009 at 09:41:49AM -0800, Quanah Gibson-Mount wrote:
We currently use postfix as a part of our overall product, which means that
it ends up being packaged inside our own RPM (or deb, etc) packages, and
then redeployed when our product is installed. One thing I've noticed
--On Monday, February 09, 2009 12:57 PM -0500 Victor Duchovni
victor.ducho...@morganstanley.com wrote:
Of the numerous software applications we
build as the underlying components to our product, Postfix is the only
one that goes to such pains. Is there a way that I'm missing to turn
off
Quanah Gibson-Mount wrote:
We currently use postfix as a part of our overall product, which means
that it ends up being packaged inside our own RPM (or deb, etc)
packages, and then redeployed when our product is installed. One thing
I've noticed about the postfix build system in this is that
On Mon, Feb 09, 2009 at 10:02:33AM -0800, Quanah Gibson-Mount wrote:
You have not read PACKAGE_README.
This is really the answer. I missed this document, things should work fine
with it.
One minor nit in the document, it uses xargs to collect a file list for
tar, but the file list may be
On Mon, Feb 09, 2009 at 01:17:08PM -0500, Victor Duchovni wrote:
On Mon, Feb 09, 2009 at 10:02:33AM -0800, Quanah Gibson-Mount wrote:
You have not read PACKAGE_README.
This is really the answer. I missed this document, things should work fine
with it.
One minor nit in the
Victor Duchovni:
On Mon, Feb 09, 2009 at 10:02:33AM -0800, Quanah Gibson-Mount wrote:
You have not read PACKAGE_README.
This is really the answer. I missed this document, things should work fine
with it.
One minor nit in the document, it uses xargs to collect a file list for
tar,
On Mon, Feb 09, 2009 at 02:13:55PM -0500, Wietse Venema wrote:
One minor nit in the document, it uses xargs to collect a file list for
tar, but the file list may be too long for one command invocation:
% cd INSTALL_ROOT
% rm -f SOMEWHERE/outputfile
% find . \! -type d
On Mon, Feb 09, 2009 at 02:59:02PM -0500, Victor Duchovni wrote:
On Mon, Feb 09, 2009 at 02:13:55PM -0500, Wietse Venema wrote:
One minor nit in the document, it uses xargs to collect a file list for
tar, but the file list may be too long for one command invocation:
% cd
On Mon, Feb 09, 2009 at 12:19:26PM -0800, Quanah Gibson-Mount wrote:
--On Monday, February 09, 2009 12:57 PM -0500 Victor Duchovni
victor.ducho...@morganstanley.com wrote:
http://www.postfix.org/PACKAGE_README.html
And just to confirm, the steps here worked beautifully, thank you. :)
Quanah Gibson-Mount:
--On Monday, February 09, 2009 12:57 PM -0500 Victor Duchovni
victor.ducho...@morganstanley.com wrote:
http://www.postfix.org/PACKAGE_README.html
And just to confirm, the steps here worked beautifully, thank you. :)
I did have to use an install root of /../
--On Monday, February 09, 2009 12:57 PM -0500 Victor Duchovni
victor.ducho...@morganstanley.com wrote:
http://www.postfix.org/PACKAGE_README.html
And just to confirm, the steps here worked beautifully, thank you. :)
I did have to use an install root of /../ since it won't take /. I
On Mon, Feb 09, 2009 at 03:41:34PM -0500, Wietse Venema wrote:
It would be nice if there was someway for it to recognize it was already
built with a prefix, so no need to go down multiple layers. But I have an
easily working solution to it. :)
It's good to hear that the instructions
14 matches
Mail list logo
