Renat Golubchyk mailto:[EMAIL PROTECTED] wrote:
You can copy the ebuild to your overlay and patch postfix from there.
If you don't have to do anything else before compiling it then it's as
trivial as epatch /path/to/postfix.patch somewhere in src_unpack().
Doing it this way has the benefit of
On Wed, 9 Nov 2005 10:23:31 +0200 Eray Aslan [EMAIL PROTECTED]
wrote:
Renat Golubchyk mailto:[EMAIL PROTECTED] wrote:
You'll just have to keep an eye for upgrades, because they
will probably come without this patch. If you want this patch to be
included in postfix create a bug in bugzilla
On Wed, 9 Nov 2005 10:23:31 +0200, Eray Aslan wrote:
You'll just have to keep an eye for upgrades, because they
will probably come without this patch. If you want this patch to be
included in postfix create a bug in bugzilla with the request.
I don't think it is a good idea. I would not
Hi!
On Tue, 8 Nov 2005 11:37:45 +0200 Eray Aslan [EMAIL PROTECTED]
wrote:
I am using portage for packet management. But there are a few
programs (postfix for example) that I have emerged and now would like
to manage myself. What is the best way to take a program out of
portage without
Renat Golubchyk mailto:[EMAIL PROTECTED] wrote:
If postfix becomes a dependency of another package in the
future it will
get updated by portage regardless of it being in the world-file.
Possible but unlikely. It is a stable mail server. I doubt we will add or
remove any software in the
On Tue, 8 Nov 2005 20:03:45 +0200 Eray Aslan [EMAIL PROTECTED]
wrote:
Renat Golubchyk mailto:[EMAIL PROTECTED] wrote:
Anyway, why do you want to manage those programs yourself?
Because of this patch for postfix:
http://sbserv.stahl.bau.tu-bs.de/~hildeb/postfix/duchovni/multi_instance.gz
6 matches
Mail list logo
