aboutsummaryrefslogtreecommitdiff
path: root/databases/rubygem-activerecord70
Commit message (Collapse)AuthorAgeFilesLines
* databases/rubygem-activerecord70: Update to 7.0.8.1Po-Chuan Hsieh2024-03-092-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord70: Update to 7.0.8Po-Chuan Hsieh2023-09-302-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord70: Update to 7.0.7.2Po-Chuan Hsieh2023-08-262-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord70: Update to 7.0.7Po-Chuan Hsieh2023-08-212-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord70: Update to 7.0.6Po-Chuan Hsieh2023-07-092-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord70: Update to 7.0.4.3Po-Chuan Hsieh2023-04-052-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord70: Update to 7.0.4.2Po-Chuan Hsieh2023-02-052-4/+4
| | | | | Changes: https://github.com/rails/rails/releases Security: CVE-2022-44566, CVE-2023-22794
* Mk/**ruby.mk: Switch from USE_RUBY=yes to USES=rubyMuhammad Moinur Rahman2023-01-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | 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
* databases/rubygem-activerecord70: Update version requirement of RUN_DEPENDSPo-Chuan Hsieh2022-12-302-5/+4
| | | | - Update WWW and clean up pkg-descr
* Remove WWW entries moved into port MakefilesStefan Eßer2022-09-071-2/+1
| | | | | | | | | | 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 MakefilesStefan Eßer2022-09-071-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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. This commit implements such a proposal and moves one of the WWW: entries of each pkg-descr file into the respective port's Makefile. A heuristic attempts to identify the most relevant URL in case there is more than one WWW: entry in some pkg-descr file. URLs that are not moved into the Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr files in order to preserve them. There are 1256 ports that had no WWW: entries in pkg-descr files. These ports will not be touched in this commit. The portlint port has been adjusted to expect a WWW entry in each port Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as deprecated. Approved by: portmgr (tcberner)
* databases/rubygem-activerecord70: Update to 7.0.3.1Po-Chuan Hsieh2022-07-182-4/+4
| | | | | Changes: https://github.com/rails/rails/releases Security: CVE-2022-32224
* databases/rubygem-activerecord70: Update to 7.0.3Po-Chuan Hsieh2022-05-132-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord70: Update to 7.0.2.4Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord70: Update to 7.0.2.3Po-Chuan Hsieh2022-03-252-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord70: Update to 7.0.2Po-Chuan Hsieh2022-03-072-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord70: Update to 7.0.1Po-Chuan Hsieh2022-01-232-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord70: Add rubygem-activerecord70 7.0.0Po-Chuan Hsieh2022-01-113-0/+40
Active Record connects classes to relational database tables to establish an almost zero-configuration persistence layer for applications. The library provides a base class that, when subclassed, sets up a mapping between the new class and an existing table in the database. In the context of an application, these classes are commonly referred to as models. Models can also be connected to other models; this is done by defining associations. Active Record relies heavily on naming in that it uses class and association names to establish mappings between respective database tables and foreign key columns. Although these mappings can be defined explicitly, it's recommended to follow naming conventions, especially when getting started with the library. WWW: https://rubyonrails.org/ WWW: https://github.com/rails/rails/tree/main/activerecord
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-29 05:39:31 +0000