[MacPorts] #19751: subversion +no_bdb still requires Berkeley DB

MacPorts noreply at macports.org
Wed May 27 12:40:11 PDT 2009


#19751: subversion +no_bdb still requires Berkeley DB
-------------------------------------+--------------------------------------
 Reporter:  com-macosforge@…         |       Owner:  dluke@…           
     Type:  defect                   |      Status:  new               
 Priority:  Normal                   |   Milestone:                    
Component:  ports                    |     Version:  1.7.1             
 Keywords:                           |        Port:  subversion        
-------------------------------------+--------------------------------------

Comment(by blair@…):

 I'm not going to do that to serf.  That implies I need to implement
 all these variants that apr-util has:

 {{{
 $ port variants apr-util
 apr-util has the variants:
         no_bdb: Build without BerkeleyDB support
         no_sqlite: Build without sqlite support
         openldap: Build with OpenLDAP support
         postgresql83: Build with postgres support (using postgresql v8.3)
         postgresql82: Build with postgres support (using postgresql v8.2)
         mysql5: Build with MySQL5 suppoprt
 }}}

 What happens when somebody upgrades from postgresql83 to 84 when that
 version
 comes out of beta?  That now becomes my problem?  No thank you.

 The real solution is to have MacPorts scan the port's *.dylib and:
    a) add those files to the files that the port provides
    b) add the otool -L output on those *dylib that are not provided by the
       port to the port's requirements.

 For now, people need to recompile all dependent ports when changing
 variants.

-- 
Ticket URL: <http://trac.macports.org/ticket/19751#comment:7>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list