[MacPorts] #35639: Unison 2.32 port

MacPorts noreply at macports.org
Wed Aug 15 15:52:17 PDT 2012


#35639: Unison 2.32 port
---------------------------------+------------------------------------------
 Reporter:  rwilcox@…            |       Owner:  macports-tickets@…                   
     Type:  submission           |      Status:  new                                  
 Priority:  Normal               |   Milestone:                                       
Component:  ports                |     Version:  2.1.2                                
 Keywords:                       |        Port:  unison, unison232, unison240         
---------------------------------+------------------------------------------

Comment(by ryandesign@…):

 I've looked into this a bit.

 I see the port only installs a single file, the actual unison executable,
 as ${prefix}/bin/unison-${branch}, and then installs a symlink
 ${prefix}/bin/unison pointing to it. So we can very easily just not
 install the symlink, and leave that for a new unison_select port to do. As
 for settings, it seems to store things in ~/Library/Application
 Support/Unison. I am hoping we don't need to change this per-version since
 I'm not sure at the moment where to do it.

 Given this naming of the executable, I might instead name the new ports
 the same (unison-2.32, unison-2.40), matching the naming recently used in
 the clang and llvm ports (clang-3.0, clang-3.1, etc.)

 The port has two variants, x11 and aqua. Without the x11 variant, only a
 command line version of the program is built. With the x11 variant, a gtk2
 GUI is added, but the command line version is still accessible, selectable
 with the `-ui` command line argument. I think it makes sense to make the
 x11 variant the default (`default_variants +x11`) that way the most full-
 featured version is installed by default. Users who don't want it can
 disable it (`sudo port install unison -x11`), now that MacPorts remembers
 disabled variants in the registry.

 The aqua variant is not a variant at all in my mind, but a completely
 separate program. Using this variant doesn't install the command line
 version at all, but instead only installs an OS X GUI. I propose that we
 break the aqua variant out into its own subport so that a user could
 install both the OS X GUI and the command line version if desired.

 There are multiple problems building the GUI on Mountain Lion (see years-
 old existing tickets) which I am in the process of hopefully correcting.

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


More information about the macports-tickets mailing list