Date: Wed, 18 Sep 2024 06:18:45 GMT From: Po-Chuan Hsieh <sunpoet@FreeBSD.org> To: ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org Subject: git: af90a28081f1 - main - www/rubygem-cssbundling-rails-rails71: Add rubygem-cssbundling-rails-rails71 1.4.1 Message-ID: <202409180618.48I6Ij0M031974@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by sunpoet: URL: https://cgit.FreeBSD.org/ports/commit/?id=af90a28081f1fd09f1727c2c585a13e3d86c878d commit af90a28081f1fd09f1727c2c585a13e3d86c878d Author: Po-Chuan Hsieh <sunpoet@FreeBSD.org> AuthorDate: 2024-09-18 05:51:39 +0000 Commit: Po-Chuan Hsieh <sunpoet@FreeBSD.org> CommitDate: 2024-09-18 06:13:05 +0000 www/rubygem-cssbundling-rails-rails71: Add rubygem-cssbundling-rails-rails71 1.4.1 Use Tailwind CSS, Bootstrap, Bulma, PostCSS, or Dart Sass to bundle and process your CSS, then deliver it via the asset pipeline in Rails. This gem provides installers to get you going with the bundler of your choice in a new Rails application, and a convention to use app/assets/builds to hold your bundled output as artifacts that are not checked into source control (the installer adds this directory to .gitignore by default). You develop using this approach by running the bundler in watch mode in a terminal with yarn build:css --watch (and your Rails server in another, if you're not using something like puma-dev). You can also use ./bin/dev, which will start both the Rails server and the CSS build watcher (along with a JS build watcher, if you're also using jsbundling-rails). --- www/Makefile | 1 + www/rubygem-cssbundling-rails-rails71/Makefile | 20 ++++++++++++++++++++ www/rubygem-cssbundling-rails-rails71/distinfo | 3 +++ www/rubygem-cssbundling-rails-rails71/pkg-descr | 12 ++++++++++++ 4 files changed, 36 insertions(+) diff --git a/www/Makefile b/www/Makefile index db2d0636b3a8..5e9712428a5b 100644 --- a/www/Makefile +++ b/www/Makefile @@ -1988,6 +1988,7 @@ SUBDIR += rubygem-crass SUBDIR += rubygem-cssbundling-rails SUBDIR += rubygem-cssbundling-rails-rails70 + SUBDIR += rubygem-cssbundling-rails-rails71 SUBDIR += rubygem-cuba SUBDIR += rubygem-d3_rails SUBDIR += rubygem-davclient diff --git a/www/rubygem-cssbundling-rails-rails71/Makefile b/www/rubygem-cssbundling-rails-rails71/Makefile new file mode 100644 index 000000000000..524fafb4d58e --- /dev/null +++ b/www/rubygem-cssbundling-rails-rails71/Makefile @@ -0,0 +1,20 @@ +PORTNAME= cssbundling-rails +PORTVERSION= 1.4.1 +CATEGORIES= www rubygems +MASTER_SITES= RG +PKGNAMESUFFIX= -rails71 + +MAINTAINER= sunpoet@FreeBSD.org +COMMENT= Bundle and process CSS with Tailwind, Bootstrap, PostCSS, Sass in Rails via Node.js +WWW= https://github.com/rails/cssbundling-rails + +LICENSE= MIT +LICENSE_FILE= ${WRKSRC}/MIT-LICENSE + +RUN_DEPENDS= rubygem-railties71>=6.0.0:www/rubygem-railties71 + +USES= gem + +NO_ARCH= yes + +.include <bsd.port.mk> diff --git a/www/rubygem-cssbundling-rails-rails71/distinfo b/www/rubygem-cssbundling-rails-rails71/distinfo new file mode 100644 index 000000000000..b7513bd9dd70 --- /dev/null +++ b/www/rubygem-cssbundling-rails-rails71/distinfo @@ -0,0 +1,3 @@ +TIMESTAMP = 1722711335 +SHA256 (rubygem/cssbundling-rails-1.4.1.gem) = 4b21273d627b21890da9155c88c67efc9274373d8b0add09149c262cf56c7ce1 +SIZE (rubygem/cssbundling-rails-1.4.1.gem) = 11776 diff --git a/www/rubygem-cssbundling-rails-rails71/pkg-descr b/www/rubygem-cssbundling-rails-rails71/pkg-descr new file mode 100644 index 000000000000..3bf0ef49a085 --- /dev/null +++ b/www/rubygem-cssbundling-rails-rails71/pkg-descr @@ -0,0 +1,12 @@ +Use Tailwind CSS, Bootstrap, Bulma, PostCSS, or Dart Sass to bundle and process +your CSS, then deliver it via the asset pipeline in Rails. This gem provides +installers to get you going with the bundler of your choice in a new Rails +application, and a convention to use app/assets/builds to hold your bundled +output as artifacts that are not checked into source control (the installer adds +this directory to .gitignore by default). + +You develop using this approach by running the bundler in watch mode in a +terminal with yarn build:css --watch (and your Rails server in another, if +you're not using something like puma-dev). You can also use ./bin/dev, which +will start both the Rails server and the CSS build watcher (along with a JS +build watcher, if you're also using jsbundling-rails).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202409180618.48I6Ij0M031974>