notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Ukraine
This referral link gives you 10% off a Fastmail.com account and gives me a discount on my Fastmail account.

Get notified when packages are built

A new feature has been added. FreshPorts already tracks package built by the FreeBSD project. This information is displayed on each port page. You can now get an email when FreshPorts notices a new package is available for something on one of your watch lists. However, you must opt into that. Click on Report Subscriptions on the right, and New Package Notification box, and click on Update.

Finally, under Watch Lists, click on ABI Package Subscriptions to select your ABI (e.g. FreeBSD:14:amd64) & package set (latest/quarterly) combination for a given watch list. This is what FreshPorts will look for.

non port: net-mgmt/p5-NetApp/distinfo

Number of commits found: 3

Friday, 7 Mar 2014
11:44 sunpoet search for other commits by this committer
- Update to 500.002
- Use single space after WWW:
- While I'm here:
  - Add LICENSE
  - Remove unnecessary MASTER_SITE_SUBDIR
  - Sort *_DEPENDS
  - Use TEST_DEPENDS

Changes:	http://search.cpan.org/dist/NetApp/CHANGES
PR:		ports/185417
Submitted by:	Hung-Yi Chen <gaod@hychen.org>
Approved by:	snowfly <snowfly@yuntech.edu.tw> (maintainer)
Original commitRevision:347374 
Sunday, 20 Mar 2011
12:54 miwi search for other commits by this committer
- Get Rid MD5 support
Original commit
Tuesday, 10 Mar 2009
15:13 rafan search for other commits by this committer
This package provides a suite of modules for managing NetApp's NAS
devices, commonly referred to as "filers".

This is the first public release of my NetApp Perl API, and although I
consider the code to be very stable, the API should be considered
experimental.  The convention I will be following regarding
non-compatible API changes is as follows.  I'm using a
major.minor.subminor release naming convention, and I will promise to
NOT make non-backwards compatible changes between subminor releases.

However, in order to allow the API to evolve, it is entirely possible
that non-backwards compatible changes will be made between minor
releases.  IOW, the major.minor release numbers can be considered an
API version.  Any changes to 1.1.0, 1.1.2, etc. must be backwards
compatible with the previous 1.1.* releases.

There is no guarantee that 1.2.0 will be 100% backwards compatible,
although such changes will be made only when justified.  The author
does not believe in infinite backwards compatibility.

WWW:    http://search.cpan.org/dist/NetApp/

PR:             ports/131166
Submitted by:   Tsung-Han Yeh <snowfly at yuntech.edu.tw>
Original commit

Number of commits found: 3