[Live-demo] [OSGeo] #1150: Problems with Pypi prevent installation of GeoNode

[OSGeo]

#1150: Problems with Pypi prevent installation of GeoNode
---------------------+------------------------------------------------------
 Reporter:  kalxas   |       Owner:  live-demo@…              
     Type:  defect   |      Status:  new                      
 Priority:  major    |   Milestone:  OSGeoLive7.0             
Component:  LiveDVD  |    Keywords:  pypi, python, geonode    
---------------------+------------------------------------------------------
Changes (by hamish):

  * keywords:  pypi => pypi, python, geonode


Comment:

 general notice:

 '''please do not use eggs, easy_install, or similar for installing common
 software on the live disc.'''

 They are really useful and nice and work well locally, but are not very
 compatible with a centralized package management system. Try to generate a
 .deb instead. it's easy. it's really easy. If you must install using one
 of these tools, make sure you install it to /usr/local/ so we have some
 chance of figuring out what the heck is going later on when softwares
 compete with "last to install their version wins". dpkg is there for us to
 use, and it's the best way to avoid the inevitable conflicts.

 howto:
   http://lists.osgeo.org/pipermail/live-demo/2013-May/007451.html


 In this case PIL is available from a standard ubuntu package, and that
 package is installed and used by other software on the disc. If $your
 installer clobbers a system package with a custom install, and that's
 causing problems for an innocent 3rd party, it's going to be $your
 installer, not theirs, which gets ''disabled without prior notice''* when
 problems arise, especially as we get closer to final releases. (* consider
 this due notice)  If you think $you need another version of some package,
 please rename it or sort it out so that you don't, it will save us a world
 of trouble later on.

 If it's just pulling in $your project and $your modules alone, and doesn't
 insist on installing then removing many system -dev packages, then it
 probably isn't going to be a problem. But if it starts pulling in other
 common-dependencies it very quickly becomes a problem, and the beauty of
 the .deb system is that it automatically detects that for us before it
 becomes a run-time bug, saving us huge amounts of time and energy as we
 try to get the final image out the door.


 thanks,
 Hamish
 (been burned way too many times by this sort of thing already)

-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1150#comment:2>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.