[[email protected]: majordomo2 packaging (gentoo as an example)]

Michael Weiser <[email protected]> Mon, 25 Dec 2006 23:45:40 +0100
Newsgroups gmane.mail.majordomo.majordomo2.devel
Message-ID <[email protected]>
Hi there,

I tried to send the following twice now but it didn't make it through.
Are attachments banned? How do I get my changes to the developers then?

----- Forwarded message from Michael Weiser <[email protected]> -----

From: Michael Weiser <[email protected]>
To: [email protected]
Date: Sun, 24 Dec 2006 17:04:07 +0100
Subject: majordomo2 packaging (gentoo as an example)

Hi list,

I've installed mj2 on my Gentoo system and it runs nicely. I really like
the idea of reusing my majordomo knowledge with a state of the art
version that's actually maintained.

To avoid (re)installation confusion I created a portage package for it.
Unfortunately the installation routine assumes to be installing into the
final runtime directory. Most packaging systems for Linux (rpm, portage,
debian?) use an intermediary image directory to install into, then
create the package from it and install the package into the runtime
system. The de-facto standard for this is to use the DESTDIR
make/environment variable. This is supported by perl's MakeMaker but not
the postinstall script.

So I did some ugly hacks to get it to work. Please find the outcome
attached to this email for consideration. Now I'm wondering if there's
already a better way to do this or someone'd be willing to clean
up my mess and include it into upstream.
-- 
Thanks in advance,
Michael

----- End forwarded message -----

-- 
tschuess, Michael
Sauced it has to be, sauced!