git: 1bd0a2378448 - main - databases/rubygem-activerecord71: Add rubygem-activerecord71 7.1.1
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 01 Nov 2023 07:59:10 UTC
The branch main has been updated by sunpoet:
URL: https://cgit.FreeBSD.org/ports/commit/?id=1bd0a2378448470bb9211b46664afc7230d428cd
commit 1bd0a2378448470bb9211b46664afc7230d428cd
Author: Po-Chuan Hsieh <sunpoet@FreeBSD.org>
AuthorDate: 2023-11-01 07:56:00 +0000
Commit: Po-Chuan Hsieh <sunpoet@FreeBSD.org>
CommitDate: 2023-11-01 07:56:00 +0000
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.
---
databases/Makefile | 1 +
databases/rubygem-activerecord71/Makefile | 25 +++++++++++++++++++++++++
databases/rubygem-activerecord71/distinfo | 3 +++
databases/rubygem-activerecord71/pkg-descr | 11 +++++++++++
4 files changed, 40 insertions(+)
diff --git a/databases/Makefile b/databases/Makefile
index 209abee417cc..77d049cc578a 100644
--- a/databases/Makefile
+++ b/databases/Makefile
@@ -917,6 +917,7 @@
SUBDIR += rubygem-activerecord60
SUBDIR += rubygem-activerecord61
SUBDIR += rubygem-activerecord70
+ SUBDIR += rubygem-activerecord71
SUBDIR += rubygem-after_commit_queue
SUBDIR += rubygem-amalgalite
SUBDIR += rubygem-arel
diff --git a/databases/rubygem-activerecord71/Makefile b/databases/rubygem-activerecord71/Makefile
new file mode 100644
index 000000000000..cf6e463b7aa1
--- /dev/null
+++ b/databases/rubygem-activerecord71/Makefile
@@ -0,0 +1,25 @@
+PORTNAME= activerecord
+PORTVERSION= 7.1.1
+CATEGORIES= databases rubygems
+MASTER_SITES= RG
+PKGNAMESUFFIX= 71
+
+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-activemodel71>=${PORTVERSION}<${PORTVERSION}_99:databases/rubygem-activemodel71 \
+ rubygem-activesupport71>=${PORTVERSION}<${PORTVERSION}_99:devel/rubygem-activesupport71 \
+ rubygem-timeout>=0.4.0:devel/rubygem-timeout
+
+USES= gem
+
+NO_ARCH= yes
+
+PORTSCOUT= limit:^7\.1\.
+
+.include <bsd.port.mk>
diff --git a/databases/rubygem-activerecord71/distinfo b/databases/rubygem-activerecord71/distinfo
new file mode 100644
index 000000000000..d1ecda15bc54
--- /dev/null
+++ b/databases/rubygem-activerecord71/distinfo
@@ -0,0 +1,3 @@
+TIMESTAMP = 1697330170
+SHA256 (rubygem/activerecord-7.1.1.gem) = f8dd03c0f3a462d616781dba3637a281ec86aaf6e643b56bea308e451ee96325
+SIZE (rubygem/activerecord-7.1.1.gem) = 540672
diff --git a/databases/rubygem-activerecord71/pkg-descr b/databases/rubygem-activerecord71/pkg-descr
new file mode 100644
index 000000000000..2ec976f87967
--- /dev/null
+++ b/databases/rubygem-activerecord71/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.