diff options
| author | Po-Chuan Hsieh <sunpoet@FreeBSD.org> | 2025-11-17 21:02:39 +0000 |
|---|---|---|
| committer | Po-Chuan Hsieh <sunpoet@FreeBSD.org> | 2025-11-17 21:06:45 +0000 |
| commit | ffad4e7c5e4d2c75f59697769ad235a1e9e11c92 (patch) | |
| tree | 5eac37d42330e1133f20dad070ec7276b764307b | |
| parent | 50e23bddce341b59265e60fc825f0b00e54c3e7c (diff) | |
databases/rubygem-activerecord81: Add rubygem-activerecord81 8.1.0
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.
| -rw-r--r-- | databases/Makefile | 1 | ||||
| -rw-r--r-- | databases/rubygem-activerecord81/Makefile | 25 | ||||
| -rw-r--r-- | databases/rubygem-activerecord81/distinfo | 3 | ||||
| -rw-r--r-- | databases/rubygem-activerecord81/pkg-descr | 11 |
4 files changed, 40 insertions, 0 deletions
diff --git a/databases/Makefile b/databases/Makefile index becd75883257..10c797a0afd3 100644 --- a/databases/Makefile +++ b/databases/Makefile @@ -944,6 +944,7 @@ SUBDIR += rubygem-activerecord71 SUBDIR += rubygem-activerecord72 SUBDIR += rubygem-activerecord80 + SUBDIR += rubygem-activerecord81 SUBDIR += rubygem-after_commit_queue SUBDIR += rubygem-amalgalite SUBDIR += rubygem-arel diff --git a/databases/rubygem-activerecord81/Makefile b/databases/rubygem-activerecord81/Makefile new file mode 100644 index 000000000000..1dd26745833f --- /dev/null +++ b/databases/rubygem-activerecord81/Makefile @@ -0,0 +1,25 @@ +PORTNAME= activerecord +PORTVERSION= 8.1.0 +CATEGORIES= databases rubygems +MASTER_SITES= RG +PKGNAMESUFFIX= 81 + +MAINTAINER= sunpoet@FreeBSD.org +COMMENT= Object-relational mapping layer for Rails MVC Framework +WWW= https://github.com/rails/rails/tree/main/activerecord \ + https://rubyonrails.org/ + +LICENSE= MIT +LICENSE_FILE= ${WRKSRC}/MIT-LICENSE + +RUN_DEPENDS= rubygem-activemodel81>=${PORTVERSION}<${PORTVERSION}_99:databases/rubygem-activemodel81 \ + rubygem-activesupport81>=${PORTVERSION}<${PORTVERSION}_99:devel/rubygem-activesupport81 \ + rubygem-timeout>=0.4.0:devel/rubygem-timeout + +USES= gem + +NO_ARCH= yes + +PORTSCOUT= limit:^8\.1\. + +.include <bsd.port.mk> diff --git a/databases/rubygem-activerecord81/distinfo b/databases/rubygem-activerecord81/distinfo new file mode 100644 index 000000000000..f19d63fd3e04 --- /dev/null +++ b/databases/rubygem-activerecord81/distinfo @@ -0,0 +1,3 @@ +TIMESTAMP = 1762526250 +SHA256 (rubygem/activerecord-8.1.0.gem) = cacfc779cc551444543ebc6021831676c185da336979606e7478d03a18d23288 +SIZE (rubygem/activerecord-8.1.0.gem) = 566784 diff --git a/databases/rubygem-activerecord81/pkg-descr b/databases/rubygem-activerecord81/pkg-descr new file mode 100644 index 000000000000..2ec976f87967 --- /dev/null +++ b/databases/rubygem-activerecord81/pkg-descr @@ -0,0 +1,11 @@ +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. |