Bug 236562 - www/p5-WWW-Mechanize-PhantomJS Deprecate port?
Summary: www/p5-WWW-Mechanize-PhantomJS Deprecate port?
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Walter Schwarzenfeld
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-15 22:54 UTC by Romain Tartière
Modified: 2019-08-13 12:13 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (pi)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Romain Tartière freebsd_committer freebsd_triage 2019-03-15 22:54:54 UTC 
Hello!

While looking for ports without a maintainer, I saw that lang/phantomjs was still in the ports tree while being discontinued one year ago and having a lot of problems (we used it at $WORK and had to switch to chrome / firefox headless some time ago).

I though it was worth deprecating it:
https://svnweb.freebsd.org/ports?view=revision&revision=495806

However, I failed at seeing that it had ports depending on it.  You will probably want to:
  - deprecate www/p5-WWW-Mechanize-PhantomJS if it is not actively worked on and set the same deprecation date on this port; or
  - revert my change (and maybe take maintainership of lang/phantomjs?)

Sorry for the late heads-up!
Comment 1 Romain Tartière freebsd_committer freebsd_triage 2019-03-15 22:58:11 UTC 
See bug 236561 for companion issue with www/grafana3
Comment 2 Walter Schwarzenfeld freebsd_triage 2019-08-13 12:13:24 UTC 
Done in ports r508624.

-->
DEPRECATED=     uses expired lang/phantomjs
EXPIRATION_DATE=2019-12-01