[csw-maintainers] netsnmp package, policy question

[Mike Watters]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dagobert Michelsen wrote:
> Hi Roger,
> 
> Am 26.03.2009 um 11:55 schrieb Roger Håkansson:
>> What is the standard regarding perl and/or python modules for
>> packages, are those to be packaged in separate packages or is it ok to
>> put them with the main package? (I guess separate, but have to ask)
> 
> Yes. See subversion as example for different Python/Ruby/Java packages:
>  
> <http://apps.sourceforge.net/trac/gar/browser/csw/mgar/pkg/subversion/trunk/Makefile>
> 
> 
>> Secondly, regarding python packages, the netsnmp install puts python
>> stuff in /opt/csw/lib/python2.6/site-packages, but I've seen other
>> packages put their stuff in /opt/csw/lib/python/site-packages (it
>> could be caused by pysetuptools which have its stuff there and which
>> is used by netsnmp install), is both ok?
> 
> This is what Mike wrote some time ago:
> 
> Am 15.03.2009 um 17:13 schrieb Mike Watters:
>>> * python eggs needed to be reinstalled with easy_install.
>>>  they were in lib/python, now they are in lib/python2.6
>>>  (but i guess this should not be a real problem ...
>>>  even if it would be nice to know why it happens)
>>
>> prefix/lib/python is a non-standard location for python installs.  I
>> packaged it up standard.
>> the "new version" should allow for eggs in prefix/lib/python.  During
>> the packaging,
>> I "patched" site.py ( the extension that tells python where all the
>> eggs are ) to search the as follows:
>>
>> lib/python2.6/site-packages:lib/python/site-packages:lib/python2.5/site-python:\
>>
>> lib/python2.3/site-python:lib/python2.1/site-python:lib/python/site-python
>>
>>
>> are your eggs in /usr/lib/python or ...python/site-packages?
> 
> 
> Maybe Mike has a preferred location?
> 
> 
> Best regards
> 
>   -- Dago

please use /opt/csw/lib/python2.6/site-packages

going forward, for an upgrade of python I will continue to patch the site.py file.
This will allow it to honor the prior python module install locations.

I check existing packages with python modules to see where they put their files,
and append the location to site.py.  The same should be true for any new releases going forward.

only if at the time of the build, no existing python modules use the depreciated locations they will be removed.
** bug report requesting update will be filed **


- --

Thanks,
Mike

"Any intelligent fool can make things bigger, more complex,
and more violent.  It takes a touch of genius -- and a lot of courage --
to move in the opposite direction."

* Albert Einstein 1879 - 1955
    US German-born Theoretical Physicist
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknLjvQACgkQLrhmsXMSLxfykwCgvhYXjwbXODCAWCetOxflHd3M
yOcAnjm/6eVLsdlz2JxXWpOuKzdzE9/A
=WWYp
-----END PGP SIGNATURE-----