[Live-demo] [OSGeo] #1409: Examine Potential Conflicts in PGDG and Current Repos for PostgreSQL

OSGeo trac_osgeo at osgeo.org
Fri Sep 19 22:12:23 PDT 2014

#1409: Examine Potential Conflicts in PGDG and Current Repos for PostgreSQL
 Reporter:  darkblueb  |       Owner:  live-demo@…              
     Type:  task       |      Status:  new                      
 Priority:  normal     |   Milestone:  OSGeoLive8.5             
Component:  LiveDVD    |    Keywords:  postgis                  
Changes (by hamish):

  * milestone:  Unplanned => OSGeoLive8.5


 Hi Brian,

 could you elaborate please? is this a request for an audit? what should
 that audit look at/for? Stepping back, what's the need + justification for
 including 3rd party packages? (ie are they critical; can we just make the
 problem go away by not including them?) What's the benefit?

 As long as everything is in .debs, conflicting files in the filesystem
 will be flagged at install time with dpkg refusing to go on. If there is a
 structural conflict, the 3rd party .debs should have a Conflicts: line in
 its debian/control file which tells dpkg not to let the two packages co-
 exist. If they don't have that Conflicts line it's a bug we should file a
 ticket with them.

 As you know, IMHO 3rd party PPAs are to be avoided as much as possible.
 :-) Especially if they touch core infrastructure packages it introduces
 many headaches for the many packages from many sources that depend on the
 original. (e.g. the fun caused by replacing official gdal packages)

 Despite appearances I'm not totally against 3rd party installs, just that
 the benefits must be shown to firmly outweigh the costs. (if I have any
 bias it's because generally I only see the cost end of this transaction
 ending up in my lap when stuff breaks)


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

More information about the Osgeolive mailing list