#46743: vcs_blackbox @1.20150203 New contribution ---------------------------+-------------------------------- Reporter: tal@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: vcs_blackbox | ---------------------------+-------------------------------- Comment (by tal@…): This is my first time submitting to Macports. I haven't heard back from anyone about this new submission. Is there something I need to do? -- Ticket URL: <https://trac.macports.org/ticket/46743#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X

#46743: vcs_blackbox @1.20150203 New contribution ---------------------------+-------------------------------- Reporter: tal@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: vcs_blackbox | ---------------------------+-------------------------------- Comment (by mojca@…): These lines use a slightly "unnatural" approach: {{{ use_configure no build {} destroot { system "cd ${worksrcpath} && make packages-macports DESTDIR=${destroot}/${prefix}" }}} It would make slightly more sense to adapt variables, for example change `destroot.target` to `packages-macports` and `destroot.destdir` to `DESTDIR=${destroot}/${prefix}"` and let MacPorts work out the rest of the "magic" Just curious: in what respect is MacPorts special, so that you need a special target in `Makefile` to handle MacPorts? Why doesn't `make install DESTDIR=${destroot}[/${prefix}]` work? Related to the comments in your Portfile. Try to delete (or comment out) the line with checksums and run {{{ port -v extract vcs_blackbox }}} This will give you the checksums you need without additional effort. It's a good practice to include both `rmd160` and `sha256`. -- Ticket URL: <https://trac.macports.org/ticket/46743#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X

#46743: vcs_blackbox @1.20150203 New contribution ---------------------------+-------------------------------- Reporter: tal@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: vcs_blackbox | ---------------------------+-------------------------------- Comment (by mojca@…): A few more comments. There is a command {{{ port -v livecheck }}} (if you are in `vcs_blackbox` already, there's no need to provide the port name, else add `vcs_blackbox` at the end of that command) that will tell you if there is a newer version available. There is no need for "1. Find tag name on github." I already told you how to update the checksums: just delete the lines and run {{{ port -v extract }}} I changed many aspects of the port to make use of the `github` `PortGroup`, so there is no need for extra settings. If you want the latest version, just replace {{{ 1.20150203 v }}} with the checksum of the commit or a tag or whatever. (Just note that you'll probably need to set the version separately if you use something like "stable".) The letter "v" is just to prepend something in front of the version to make a tag. -- Ticket URL: <https://trac.macports.org/ticket/46743#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X

#46743: vcs_blackbox @1.20150203 New contribution ---------------------------+-------------------------- Reporter: tal@… | Owner: ryandesign@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: vcs_blackbox | ---------------------------+-------------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => ryandesign@… * status: new => assigned -- Ticket URL: <https://trac.macports.org/ticket/46743#comment:11> MacPorts <https://www.macports.org/> Ports system for OS X