Bugzilla Bug 56673

*****BETA BETA BETA BETA BETA*****
works for me (but haven't tested every new feature)

FEATURES: http://www.qcc.ca/~charlesc/software/getmail-4/documentation.html#features



* changed DEPEND="virtual/python" (getmail-3) to DEPEND=">=dev-lang/python-2.3.3"
* right now there are 2 doc dirs (ugly) but this problem will be gone after getmail is out off beta stage

Reproducible: Always
Steps to Reproduce:

Created an attachment (id=35174) [edit]
getmail-4.0.0_beta1.ebuild

Created an attachment (id=35461) [edit]
SLOTed & renaming ebuild

I also wrote my own ebuild file for getmail-4.0.0_beta3.

This one is a different approache because of the config file change, I must
have the ability to run both versions in parallel. Here is the result, it
renames the binaries and the ebuild is SLOTed.

Not excessively tested, but works.

******* OFFICIAL RELEASE ***************

My ebuild works flawlessly (at least for me).

@Bernd:
I don't need SLOT support. For me getmail offers everything i need.

I think (i.e. i am not good in python and python paths) you should change the path
"insinto /usr/lib/python2.3/site-packages/getmailcore"
to something that will work with newer python versions too.

Sure, in the view of features or benefits, no one needs getmail v3 (or prior).

But if you replace getmail version 3 wih getmail version 4 on a server that has a significant amount of users and every user has a getmail-config file and a cronjob that uses getmail to fetch his mail, you *cannot* just replace the getmail binary. The users will get errors over errors instead of their mail.

For my specific purposes, the amount of users is not that much and I will get my users to switch to the new getmail config files when I upgrade.
But I think it's important to keep care about servers that can not replace a frequently used binary by another one that does not work with the existing configs.

The installation in python-2.3-directory is imho correct as long as the dependancy of getmail is exactly python-2.3.

If one decides not to use slotting, you can just run the included setup routine, it will do the rest and make the ebuild much easier. I would not do this in the official ebuild because of the given problems when upgrading.

getmail-4.0.1 committed to CVS with SLOT. Please test and thanks for reporting.

Cheers,
Tuan