[MacPorts] #23598: Python error activatin duplicity

[MacPorts]

#23598: Python error activatin duplicity
-----------------------------+----------------------------------------------
 Reporter:  isaac@…          |       Owner:  singingwolfboy@…           
     Type:  defect           |      Status:  assigned                   
 Priority:  Normal           |   Milestone:                             
Component:  ports            |     Version:  1.8.2                      
 Keywords:                   |        Port:  duplicity                  
-----------------------------+----------------------------------------------

Comment(by singingwolfboy@…):

 Replying to [comment:13 snc@…]:
 > I'm not convinced the port needs to manually link the binaries.
 PortGroup python26 does this for you have linkbinaries set to yes.
 >
 > Is simply removing your post-destroot acceptable?

 I didn't know about python.linkbinaries. Nifty! I looked over your diff,
 and I see two main problems:

  * The port should be named "duplicity", not "py26-duplicity"
  * The port does not create "/opt/local/bin/duplicity", it creates
 "/opt/local/bin/duplicity-2.6"

 Duplicity is not a Python module, it's a separate program that happens to
 use Python as a dependency. It so happens that duplicity is written in
 Python, but I don't think that makes a difference. People who want to use
 duplicity for backup shouldn't have to care about which Python branch they
 use, although if they do care, they should be able to set it. (However, at
 this point, I think it's an acceptable price to drop multi-branch support
 in this port in order to just get duplicity working. Latest 2.X branch is
 a reasonable default.)

 snc, would you be OK with me using your diff, but changing the name to
 "duplicity" and creating a post-destroot section to create a symbolic link
 from ${prefix}/bin/duplicity to ${prefix}/bin/duplicity-2.6 ?

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