Bug 212012 - [NEW PORT] devel/rtags: Indexer for C and C++
Summary: [NEW PORT] devel/rtags: Indexer for C and C++
Status: Closed Not Accepted
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Rodrigo Osorio
URL:
Keywords: feature, needs-qa
Depends on:
Blocks:
 
Reported: 2016-08-20 14:02 UTC by wandns
Modified: 2017-12-03 21:28 UTC (History)
3 users (show)

See Also:
koobs: maintainer-feedback? (wandns)


Attachments
shell archive of rtags port (4.28 KB, text/plain)
2016-08-20 14:02 UTC, wandns
koobs: maintainer-approval+
Details
RTags version 2.9 (3.84 KB, text/plain)
2017-04-04 21:50 UTC, wandns
no flags Details
rtags v2.15 (3.70 KB, text/plain)
2017-11-21 19:27 UTC, Rodrigo Osorio
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description wandns 2016-08-20 14:02:25 UTC
Created attachment 173895 [details]
shell archive of rtags port
Comment 1 Pawel Pekala freebsd_committer freebsd_triage 2016-08-26 20:53:14 UTC
Please test before submitting:

https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing.html


===> Portlint output:
FATAL: Makefile: [3]: use a tab (not space) after a variable name
FATAL: Makefile: [4]: use a tab (not space) after a variable name
FATAL: Makefile: [5]: use a tab (not space) after a variable name
FATAL: Makefile: [6]: use a tab (not space) after a variable name
FATAL: Makefile: [8]: use a tab (not space) after a variable name
FATAL: Makefile: [9]: use a tab (not space) after a variable name
FATAL: Makefile: [11]: use a tab (not space) after a variable name
FATAL: Makefile: [13]: use a tab (not space) after a variable name
FATAL: Makefile: [14]: use a tab (not space) after a variable name
WARN: Makefile: [15]: use a tab (not space) after a variable name
WARN: Makefile: [16]: use a tab (not space) after a variable name
FATAL: Makefile: [18]: use a tab (not space) after a variable name
WARN: Makefile: [19]: use a tab (not space) after a variable name
WARN: Makefile: [20]: use a tab (not space) after a variable name
WARN: Makefile: [21]: use a tab (not space) after a variable name
WARN: Makefile: [22]: use a tab (not space) after a variable name
WARN: Makefile: [24]: use a tab (not space) after a variable name
FATAL: Makefile: [26]: use a tab (not space) after a variable name
FATAL: Makefile: [28]: use a tab (not space) after a variable name
12 fatal errors and 7 warnings found.
Comment 2 wandns 2016-09-16 17:54:08 UTC
I followed the instructions at https://www.freebsd.org/doc/en/books/porters-handbook/own-port.html and there were no portlint warnings. It seems the testing instructions in section 3.4 and 3.5 don't match the ones in your link. I'll follow the ones in your link and update this port.
Comment 3 Dmitry Marakasov freebsd_committer freebsd_triage 2017-02-22 14:08:54 UTC
Any progress here?
Comment 4 wandns 2017-04-04 21:50:48 UTC
Created attachment 181492 [details]
RTags version 2.9
Comment 5 wandns 2017-04-04 21:53:52 UTC
I finally had time to update this port. Please use the latest attachment.
Comment 6 wandns 2017-06-16 20:25:46 UTC
Any progress?
Comment 7 Kubilay Kocak freebsd_committer freebsd_triage 2017-06-17 01:10:57 UTC
@wandns Does the port now pass QA (both portlint, poudriere) ?

There are also minor issues:

* Add LICENCE_FILE if one exists within distribution file(${WRKSRC}/path/to/license)
* Combine individual USES lines into one
Comment 8 wandns 2017-11-19 20:00:56 UTC
I'm no longer using FreeBSD as a development platform because some of the proprietary development tools I must use do not run on it. Therefore, it's unlikely that I will have time to contribute to this port at this time.
Comment 9 Rodrigo Osorio freebsd_committer freebsd_triage 2017-11-21 19:27:42 UTC
Created attachment 188181 [details]
rtags v2.15
Comment 10 Rodrigo Osorio freebsd_committer freebsd_triage 2017-11-21 19:29:59 UTC
wandns@ : I upload a new shar for the rtags port v2.15. Are you interested in maintain this port ? Otherwise I'll take the maintenership and commit it.
Comment 11 wandns 2017-11-21 22:27:13 UTC
Thanks for being willing to take maintainership of this. I think that would be best since I'm not using FreeBSD at this time.
Comment 12 Rodrigo Osorio freebsd_committer freebsd_triage 2017-12-03 21:28:58 UTC
The submitter change its mind and doen't want to submit this port anymore