On Fri, 30 Sep 2005 11:42:10 -0500, Kerin Millar <[EMAIL PROTECTED]>
wrote:
On 9/29/05, Mike Myers <[EMAIL PROTECTED]> wrote:
Hi,
I have a qmail server configured, for the most part similar to the docs
on
the gentoo site. I was wondering though if there was a way to archive
all
the email messages. I saw a tool to do that on the inter7 site, but it
said it was a patch to allow archiving. i'm not too sure how to patch
some code when it's in portage, and i don't really want to reinstall
qmail
Create a portage overlay (for example, at /usr/local/portage) and copy
the existing mail-mta/qmail structure into it. Drop your patch in at
mail-mta/qmail/files then add a statement to patch it in within the
src_unpack() function of the ebuild:
epatch ${FILESDIR}/foo.patch
You'll see many such examples in the ebuild as it is. Alternatively
you could `ebuild unpack` the ebuild in the main portage tree, patch
the source in the working directory manually before concluding with an
`ebuild qmerge" statement (a less desirable approach in my view). For
further details this wiki entry may help:
http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds
With regards to the first approach you'll need to make sure that you
revise your customised ebuild if there are any future qmail revision
bumps otherwise your overlay copy will be superceded by the upgrade in
the mainline portage tree.
Another possibility is to file a bug referencing the patch, add the
keyword "Inclusion" and assign to [EMAIL PROTECTED] asking for this
patch to be included.
Regards,
--Kerin
Thanks for the info. Unfortunately, neither suggestion worked. It seems
to me like the qmail-tap patch conflicts with the other numerous patches
that qmail needs, so it's unable to find the parts of file it needs to
patch. I've filed a bug report, but it was closed and marked 'invalid',
and considered a 'help request'. So, no dice there. I posted the issue
in the forums, so now there are two threads concerning the qmail-tap
patch, but neither have replies. I'm not really certain where to go next.
Thanks,
Mike
--
[email protected] mailing list
