| Port details |
- rubygem-activerecord71 Object-relational mapping layer for Rails MVC Framework
- 7.1.3.2 databases
 =0      7.1.3.2Version of this port present on the latest quarterly branch. - Maintainer: sunpoet@FreeBSD.org
- Port Added: 2023-11-01 08:00:28
- Last Update: 2024-03-09 14:07:01
- Commit Hash: 8d4b2d7
- Also Listed In: rubygems
- License: MIT
- WWW:
- https://github.com/rails/rails/tree/main/activerecord
- https://rubyonrails.org/
- Description:
- 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.
  ¦  ¦  ¦  ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- rubygem-activerecord71>0:databases/rubygem-activerecord71
- To install the port:
- cd /usr/ports/databases/rubygem-activerecord71/ && make install clean
- To add the package, run one of these commands:
- pkg install databases/rubygem-activerecord71
- pkg install rubygem-activerecord71
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: rubygem-activerecord71
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1709391048
SHA256 (rubygem/activerecord-7.1.3.2.gem) = 4872900c3340948e2fc92ea08397034eaacd8cec1760ed7704975a116cc78173
SIZE (rubygem/activerecord-7.1.3.2.gem) = 544256
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- ruby32 : lang/ruby32
- gem : devel/ruby-gems
- Runtime dependencies:
-
- rubygem-activemodel71>=7.1.3.2<7.1.3.2_99 : databases/rubygem-activemodel71
- rubygem-activesupport71>=7.1.3.2<7.1.3.2_99 : devel/rubygem-activesupport71
- rubygem-timeout>=0.4.0 : devel/rubygem-timeout
- ruby32 : lang/ruby32
- gem : devel/ruby-gems
- Patch dependencies:
-
- ruby32 : lang/ruby32
- gem : devel/ruby-gems
-
- This port is required by:
- for Run
-
- databases/rubygem-flipper-active_record
- databases/rubygem-pghero
- mail/rubygem-actionmailbox71
- net/rubygem-activestorage71
- textproc/rubygem-actiontext71
- www/rubygem-rails71
Configuration Options:- No options to configure
- Options name:
- databases_rubygem-activerecord71
- USES:
- gem
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 4
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
7.1.3.2
09 Mar 2024 14:07:01
 |
Po-Chuan Hsieh (sunpoet) |
databases/rubygem-activerecord71: Update to 7.1.3.2
Changes: https://github.com/rails/rails/releases |
7.1.3
21 Feb 2024 15:11:00
|
Po-Chuan Hsieh (sunpoet) |
databases/rubygem-activerecord71: Update to 7.1.3
Changes: https://github.com/rails/rails/releases |
7.1.2
14 Nov 2023 17:16:35
|
Po-Chuan Hsieh (sunpoet) |
databases/rubygem-activerecord71: Update to 7.1.2
Changes: https://github.com/rails/rails/releases |
7.1.1
01 Nov 2023 07:56:00
|
Po-Chuan Hsieh (sunpoet) |
databases/rubygem-activerecord71: Add rubygem-activerecord71 7.1.1
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. |
Number of commits found: 4
|
As an Amazon Associate I earn from qualifying purchases.