Summary: | [NEW PORT] www/wp-cli: Command line interface for WordPress | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Vick Khera <vivek> | ||||
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||
Status: | Closed Feedback Timeout | ||||||
Severity: | Affects Only Me | CC: | miwi | ||||
Priority: | --- | Keywords: | easy, feature, needs-qa, patch | ||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Hi Vick, sorry for the delay and thanks for your contribution. On a quick glance I can see that the port needs some changes made, including: * Using the USE_GITHUB and GH_* bits. See: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#makefile-master_sites-github-description And a few examples: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#makefile-master_sites-github-ex1 * Remove leading "A " from the beginning of COMMENT * DISTNAME doesn't appear to be necessary (as it defaults to PORTNAME-PORTVERSION) It's worth running submissions through QA tools prior to submission as well: * portlint -AC * poudriere testport |
Created attachment 170410 [details] Shar file of new port www/wp-cli Command line interface to wordpress. I was unable to figure out how to make it fetch the file using the Github knobs in the port file, so I mimicked a port that installs a java app via jar file.