Bugzilla Bug 59101

Hi.

I changed the getmail v4 ebuild to install in /usr/lib/python2.3/sitepackages
just as it should. This fixes a problem when getmail is run from a cron job or
similar that it could not find the getmailcore module.
See [1], but don't take it personally :-) I also added a check if getmail v3 is
really installed and only rename executables if in that case. Beware that this
way a getmail v3 install would stomp over an v4 install. This should be fixed
in the v3 ebuild imo.

[1] http://marc.theaimsgroup.com/?l=getmail&m=109139297503155&w=2

Bye
Frank Benkstein.

Created an attachment (id=36608) [edit]
getmail-4.0.2-r1.ebuild

If you have not reported this bug, I wouldn't known that I have been threatened
to be strangled by upstream.:)
Back to the issue, from pkg_setup and pkg_postinst:

 * getmail version 4 has been completely rewritten. Visit:
http://www.qcc.ca/~charlesc/software/getmail-4/documentation.html#v4differences
 * for changes it might affect you upgrading from getmail version 3.

 * This version has been SLOTTED to co-exist with getmail 3.
 * The three main scripts are getmail4, getmail_maildir4, getmail_mbox4.
 * Please remember to `env-update; source /etc/profile` before the first use.

 * Waiting 15 seconds before continuing...
It's clearly tell the user to run `env-update; source /etc/profile` which will
update enviroment variable PYTHONPATH=/usr/lib/getmail-4.0.2 which is exactly
what I've from
http://www.qcc.ca/~charlesc/software/getmail-4/documentation.html#installing

[quote]
Installing the getmailcore package in a non-standard location
Note:  if you use one of the above methods to install the getmailcore package
into a directory other than the default, the three scripts (getmail,
getmail_maildir, and getmail_mbox) will almost certainly be unable to locate
the required files from the getmailcore package, because they will not be in a
directory in the standard Python module search path.  You will need to do one
of the following to make those files available to the scripts:

* set the environment variable PYTHONPATH to tell Python where to find the
appropriate modules.  See the documentation at the Python.org website for
details.
...
[/quote]

the reason this packages get installed to /usr/lib/getmail is from my
understanding, prefix/lib/python-python-version/site-packages/ is the location
for user installed packages, not from vendor.

Please point upstream to this bug and please let me know if the cron is not
working even after you run `env-update; source /etc/profile`.

Cheers,
Tuan

[quote]
the reason this packages get installed to /usr/lib/getmail is from my understanding, prefix/lib/python-python-version/site-packages/ is the location for user installed packages, 
not from vendor.
[/quote]

Hm, but it seems to be used by many other ebuilds, too. I have there pyxmms,
pyogg, nicotine, positron and many others. None of my installed python packages
sets PYTHONPATH.

[quote]
Please point upstream to this bug and please let me know if the cron is not working even after you run `env-update; source /etc/profile`.
[/quote]

Yeah, it is working, but you have to source /etc/profile in every crontab which
is a little bit to much overhead IMO. Please just install it to site-packages as
the other packages do and we're all happy :-)

Btw this warn function is really annoying.

I admit that I've overlook the cron thingy. It is my fault. Since getmail-4.*
is ~x86, I am expected that I will get bug report and fix it instead getting
into a  mess like this. I saw that the author have changed the instruction
page, bump to a newer version with an entry in CHANGELOG:

  -changes to my release process; the current version's URL will not change
  when a new version is released.  See, I try to help others, even when they
  don't do the same...

I've check your ebuild, everything looks good. I'll bump this to get myself out
of this mess. For the next version bump, please assign to net-mail@g.o instead
of langthang@g.o.

Thanks,
Tuan

> For the next version bump, please assign to net-mail@g.o instead of
> langthang@g.o.

I will. I just wanted to see this resolved as soon as possible and have
seen you as the responsible dev.