Port details |
- rubygem-mechanize26 WWW::Mechanize, a handy web browsing ruby object
- 2.6.0_1 www
=0 2.6.0_1Version of this port present on the latest quarterly branch.
- DEPRECATED: Use www/rubygem-mechanize instead
This port expired on: 2017-02-28
- Maintainer: ruby@FreeBSD.org
- Port Added: 2014-05-19 04:18:06
- Last Update: 2017-02-28 11:59:59
- SVN Revision: 435047
- Also Listed In: rubygems
- License: MIT
- WWW:
- https://github.com/sparklemotion/mechanize
- Description:
- The Mechanize library is used for automating interaction with websites.
Mechanize automatically stores and sends cookies, follows redirects,
can follow links, and submit forms. Form fields can be populated and
submitted. Mechanize also keeps track of the sites that you have visited as
a history.
WWW: https://github.com/sparklemotion/mechanize
-
cgit ¦ GitHub ¦ GitHub ¦ GitLab ¦
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- rubygem-mechanize26>0:www/rubygem-mechanize26
- No installation instructions:
- This port has been deleted.
- PKGNAME: rubygem-mechanize26
- Flavors: there is no flavor information for this port.
- distinfo:
- SHA256 (rubygem/mechanize-2.6.0.gem) = 0c5c3af20d1800623a5ab3d4fb40e94d4d2e83ab1b2e30fc9f5ebee0765f160d
SIZE (rubygem/mechanize-2.6.0.gem) = 131584
No package information for this port in our database- Sometimes this happens. Not all ports have packages. Perhaps there is a build error. Check the fallout link:
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- ruby23 : lang/ruby23
- gem23 : devel/ruby-gems
- Runtime dependencies:
-
- rubygem-domain_name>=0.5.1 : net/rubygem-domain_name
- rubygem-http-cookie>=1.0.0 : www/rubygem-http-cookie
- rubygem-mime-types1>=0 : misc/rubygem-mime-types1
- rubygem-net-http-digest_auth11>=0 : www/rubygem-net-http-digest_auth11
- rubygem-net-http-persistent25>0 : www/rubygem-net-http-persistent25
- rubygem-nokogiri14>=1.4 : textproc/rubygem-nokogiri14
- rubygem-ntlm-http>=0.1.1 : www/rubygem-ntlm-http
- rubygem-webrobots>=0.0.9 : www/rubygem-webrobots
- ruby23 : lang/ruby23
- gem23 : devel/ruby-gems
- Patch dependencies:
-
- ruby23 : lang/ruby23
- gem23 : devel/ruby-gems
-
- There are no ports dependent upon this port
Configuration Options:
- No options to configure
- Options name:
- N/A
- USES:
- gem
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
Commit | Credits | Log message |
2.6.0_1 28 Feb 2017 11:59:59 |
rene |
Remove expired ports:
2017-02-28 textproc/rubygem-nokogiri14: Use textproc/rubygem-nokogiri instead
2017-02-28 textproc/rubygem-liquid2: Use textproc/rubygem-liquid instead
2017-02-28 www/rubygem-rack14: Use www/rubygem-rack or www/rubygem-rack16
instead
2017-02-28 www/rubygem-mechanize26: Use www/rubygem-mechanize instead
2017-02-28 www/rubygem-net-http-persistent25: Use
www/rubygem-net-http-persistent2 instead
2017-02-28 devel/rubygem-builder32: Use devel/rubygem-builder instead
2017-02-28 www/rubygem-net-http-digest_auth11: Use
www/rubygem-net-http-digest_auth instead
2017-02-28 devel/rubygem-bson1: Use devel/rubygem-bson instead
2017-02-28 devel/rubygem-minitest4: Use devel/rubygem-minitest instead
2017-02-28 java/jdk16-doc: Should have been removed with linux-sun-jdk16
(2014-05-11)
2017-02-28 java/jdk7-doc: Should have been removed with linux-sun-jdk17
(2016-04-24)
2017-02-28 textproc/rubygem-sass-rails4: Use textproc/rubygem-sass-rails5
instead |
2.6.0_1 28 Jan 2017 20:53:53 |
sunpoet |
Mark DEPRECATED and set EXPIRATION_DATE to 2017-02-28 |
2.6.0_1 19 May 2016 10:53:06 |
amdmi3 |
- Fix trailing whitespace in pkg-descrs, categories [p-x]*
Approved by: portmgr blanket |
2.6.0_1 27 Apr 2016 21:57:32 |
swills |
Convert USES=gem:autoplist to USES=gem since autoplist is default |
2.6.0_1 27 Apr 2016 16:36:42 |
swills |
create USES=gem and update rubygem- ports to use it
Note that for now ports still have to have USE_RUBY=yes to use USES=gem
PR: 209041
Differential Revision: https://reviews.freebsd.org/D6070 |
2.6.0_1 01 Apr 2016 14:33:58 |
mat |
Remove ${PORTSDIR}/ from dependencies, categories v, w, x, y, and z.
With hat: portmgr
Sponsored by: Absolight |
2.6.0_1 17 Jan 2016 13:11:40 |
sunpoet |
- Add LICENSE_FILE
Sponsored by: PortsCamp Taiwan |
2.6.0_1 16 Aug 2015 00:42:20 |
sunpoet |
- Add NO_ARCH
- Update WWW |
2.6.0_1 31 Aug 2014 02:34:33 |
swills |
www/rubygem-mechanize26: limit portscout to proper versions |
2.6.0_1 26 Aug 2014 19:14:31 |
swills |
www/rubygem-mechanize26: tell portscout to ignore this port |
2.6.0_1 26 Aug 2014 18:45:59 |
swills |
misc/rubygem-mime-types117: rename to misc/rubygem-mime-types1
Update misc/rubygem-mime-types117 to the latest version that will work with
rails 3.x and rename to properly reflect the version. |
2.6.0 19 Aug 2014 15:35:36 |
swills |
many ruby/rubygem ports: death of rubyforge.org
rubyforge.org shutdown on May 15, 2014. This commit accounts for that by doing
several things:
- Deprecate ruby that had only rubyforge.org as MASTER_SITES (and so are now
only fetchable via our cache)
- Deprecate ports that depend on those
- Update the WWW pkg-descr line that points to rubyforge.org for rubygem ports
(which are still fetchable from rubygems.org)
The next step will be to remove rubyforge.org from bsd.sites.mk, after these
deprecated ports are deleted.
Phabric: D591
With hat: ruby
Approved by: portmgr (because of committing to unstaged graphics/mingplot port) |
2.6.0 08 Jun 2014 08:42:22 |
antoine |
Unbreak by fixing a typo (i think) |
2.6.0 19 May 2014 04:17:52 |
rpaulo |
Add rubygem-kensa v2.0.2.
This brings the following additional ports
* devel/rubygem-launch22
* misc/rubygem-mime-types117
* textproc/rubygem-nokogiri14
* www/rubygem-heroku-nav
* www/rubygem-mechanize26
* www/rubygem-net-http-digest_auth11
* www/rubygem-net-http-persistent25
With the exception of heroku-nav, all the other ports are just older versions
of already existing ports.
Reviewed by: swills |