Bug 203230

Summary: [new port] devel/rubygem-whenever
Product: Ports & Packages Reporter: Torsten Zühlsdorff <ports>
Component: Individual Port(s)Assignee: Po-Chuan Hsieh <sunpoet>
Status: Closed Overcome By Events    
Severity: Affects Only Me CC: mose
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
shar with new port none

Description Torsten Zühlsdorff 2015-09-21 12:09:24 UTC
Created attachment 161227 [details]
shar with new port

This rubygem add a clean ruby syntax for writing and deploying cron jobs.

It also is a direct dependency of the GitLab 8 version, which will be released the next days. Therefore i've already starting the update process for www/gitlab in PR 202468. :)
Comment 1 mose 2015-11-21 02:03:28 UTC
Great addition!

but I got a 
====> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
Error: Orphaned: bin/whenever
Error: Orphaned: bin/wheneverize
===> Checking for items in pkg-plist which are not in STAGEDIR
===> Error: Plist issues found.
*** Error code 1

Maybe those bin/* files need to be added manually to the PLIST_FILES after the RUBYGEM_AUTOPLIST ?
Comment 2 Torsten Zühlsdorff 2015-11-23 11:38:12 UTC
Hello mose,

this error was not there 2 months ago ;)

Do you need this port?

I wrote it as an needed dependency for GitLab 8.x - but in the new releases it is not needed anymore. If you did not need this port explicitly i will close the PR. Otherwise i will take a look and fix it.

Greetings,
Torsten
Comment 3 mose 2015-11-23 12:56:59 UTC
Hi Torsten,

No I have no need for this port for anything. I was just wandering around in the PRs testing things randomly. I guess this can be closed.

cheers,
mose
Comment 4 Torsten Zühlsdorff 2015-11-23 13:12:40 UTC
Thanks for the feedback - and the test of course! :)

I will close this PR, because it is not needed for GitLab 8.1 or greater and was only written for GitLab.
Comment 5 Kubilay Kocak freebsd_committer freebsd_triage 2015-11-23 13:43:09 UTC
@Torsten, please update the Depends (or Blocks) for this issue, as bug 203169 is still referenced.
Comment 6 Torsten Zühlsdorff 2015-11-23 13:46:49 UTC
@Kubilay - i'm sorry. I was under the impression that it will "deblock" automatically like in other issue trackern. I should have double checked this.

I removed the block and close the PR again. Thanks for the hint!