[MacPorts] #26454: Update for tovid to version 0.33

MacPorts noreply at macports.org
Sun Sep 12 15:48:29 PDT 2010


#26454: Update for tovid to version 0.33
-----------------------------------+----------------------------------------
 Reporter:  danielb@…              |       Owner:  macports-tickets@…                   
     Type:  update                 |      Status:  new                                  
 Priority:  Normal                 |   Milestone:  MacPorts 1.9.2                       
Component:  ports                  |     Version:  1.9.1                                
 Keywords:  tovid, 0.33            |        Port:  tovid                                
-----------------------------------+----------------------------------------

Comment(by danielb@…):

 Replying to [ticket:26454 danielb@…]:

 I think I know how to get this to work without the destroot.destdir line
 but I am still trying to figure out how this things works. I need to link
 the scripts to:

 ${prefix}/lib/${name}

 I am just not sure what commands to use at this point or where to call
 them from...I am thinking post-destroot? I am struggling with trying to
 figure out the difference between ${worksrcpath}, ${desroot}, and
 ${prefix}....help? :)

 > Hello all I am attempting to update the tovid port to version 0.33 which
 has some python dependencies, etc. I have a few issues with how it's
 building and this is my first stab at writing a Portfile. If add this line
 I can get tovid to actually install and run properly:
 >
 > +destroot.destdir    --prefix=${prefix} --root=${destroot}
 >
 > However it installs all the python modules to /opt/local/lib/python2.6
 /site-packages which is not in sys.path so running 'tovid gui' fails to
 find libtovid.guid module.
 >
 > If I remove this line it will install everything in the long "framework"
 path but then the 'tovid' binary fails to find the shell scripts and it
 names it to tovid-2.6 which is silly. I believe the binary is expecting
 the bash script to be located in ${prefix}/lib or what not. So in essence
 I am looking for the proper way to use the python port group and get this
 running. Any guidance would be appreciated.
 >
 > I've also patched the source to use the 'g' prefix utils in coreutils
 which I have attached. Finally, as soon as I get the build things worked
 out the last item would be to replace the Linux specific bash code that
 gleams info out of /proc/cpuinfo with proper sysctl calls that is portable
 across the supported OS X versions. I may be getting some help on those
 patches but I am pretty confident that I can fix that portion of the code
 myself if needed.
 >
 > Any help or suggestions would be appreciated. I am going to keep
 plugging away.
 >
 > Thank you,
 >
 > Dan (a.k.a., chillywilly on #macports)

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


More information about the macports-tickets mailing list