This project is based on the need for a private message system for ging /
social_stream. Instead of creating our core message system heavily dependent on
our development, we are trying to implement a generic and potent messaging gem.
After looking for a good gem to use we noticed the lack of messaging gems and
functionality in them. Mailboxer tries to fill this void delivering a powerful
and flexible message system. It supports the use of conversations with two or
more participants, sending notifications to recipients (intended to be used as
system notifications "Your picture has new comments", "John Doe has updated his
document", etc.), and emailing the messageable model (if configured to do so).
It has a complete implementation of a Mailbox object for each messageable with
inbox, sentbox, and trash.
The gem is constantly growing and improving its functionality. As it is used
with our parallel development ging / social_stream we are finding and fixing
bugs continuously. If you want some functionality not supported yet or marked as
TODO, you can create an issue to ask for it. It will be great feedback for us,
and we will know what you may find useful in the gem.
ASCII'ze port descriptions which were (ab)using UTF-8 punctuation
While here, run these files through a spell-checker and wrap some
overly long lines and/or dangling prepositions (when appropriate).
Mk/**ruby.mk: Switch from USE_RUBY=yes to USES=ruby
Switch from Mk/bsd.ruby.mk to Mk/Uses/ruby.mk
Notable changes are.
- Mk/bsd.ruby.mk is moved to Mk/Uses/ruby.mk.
- USE_RUBY=yes is replaced with USES=ruby.
- USE_RUBY_EXTCONF is replaced with USES=ruby:extconf.
- USE_RUBY_RDOC is replaced with USES=ruby:rdoc.
- USE_RUBY_SETUP is replaces with USES=ruby:setup.
- RUBY_NO_BUILD_DEPENDS and RUBY_NO_RUN_DEPENDS are replaced with
USES=ruby:{build,none,run}.
- RUBY_REQUIRE isn't used anywhere, so removed.
- USES=gem now implies USES=ruby.
This is mainly the work of yasu@ at https://reviews.freebsd.org/D27863
I have just made some cosmetic changes and ran exp-run to test that the
tree is not in a BROKEN state.
Approved by: portmgr
Differential Revision: https://reviews.freebsd.org/D37925
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
mail: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* <ashish@FreeBSD.org>
* Aaron Dalton <aaron@FreeBSD.org>
* Adam David <adam@FreeBSD.org>
* Adam McDougall <mcdouga9@egr.msu.edu>
* Adam Weinberger <adamw@FreeBSD.org>
* Ade Lovett <ade@FreeBSD.org>
* Akinori MUSHA aka knu <knu@idaemons.org>
* Alex Deiter <tiamat@komi.mts.ru>
* Alex Dupre <ale@FreeBSD.org>
* Alex Dupre <sysadmin@alexdupre.com>
* Alex Perel <veers@disturbed.net>
(Only the first 15 lines of the commit message are shown above )
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
- Add rubygem-mailboxer 0.13.0
This project is based on the need for a private message system for ging /
social_stream. Instead of creating our core message system heavily dependent on
our development, we are trying to implement a generic and potent messaging gem.
After looking for a good gem to use we noticed the lack of messaging gems and
functionality in them. Mailboxer tries to fill this void delivering a powerful
and flexible message system. It supports the use of conversations with two or
more participants, sending notifications to recipients (intended to be used as
system notifications "Your picture has new comments", "John Doe has updated his
document", etc.), and emailing the messageable model (if configured to do so).
It has a complete implementation of a Mailbox object for each messageable with
inbox, sentbox and trash.
The gem is constantly growing and improving its functionality. As it is used
with our parallel development ging / social_stream we are finding and fixing
bugs continously. If you want some functionality not supported yet or marked as
TODO, you can create an issue to ask for it. It will be great feedback for us,
and we will know what you may find useful in the gem.
WWW: https://github.com/mailboxer/mailboxer
