svn commit: r464421 - head/security/rubygem-devise_pam_authenticatable2

[Joseph Mingrone]

Sunpoet Po-Chuan Hsieh <sunpoet at freebsd.org> writes:
> I fetch the update list from portscout.
> And I won't spend time to check why a port on that list was added to the
> tree unless it has suffix for specific version or dependency.

This is approach is not working, because there is regular breakage.
What do you propose?  Should I be adding a suffix to every
net-im/mastodon dependency, or creating a separate port for each
dependency?  I would create a private revision for all of Mastodon's
dependencies, but not all of them have NO_ARCH=yes, so this would be a
pain.

If you use portscout, I do not see why it is so hard to click on the
link that takes you to freshports.org.  If you see the gem is required
by some of the larger Ruby ports like GitLab or Mastodon, then perhaps
investigate further, or simply do not bump DISTVERSION.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 962 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-ports-head/attachments/20180315/24909e9e/attachment-0001.sig>