diff options
Diffstat (limited to 'devel')
-rw-r--r-- | devel/rubygem-webpacker4-rails50/Makefile | 26 | ||||
-rw-r--r-- | devel/rubygem-webpacker4-rails50/distinfo | 3 | ||||
-rw-r--r-- | devel/rubygem-webpacker4-rails50/pkg-descr | 9 |
3 files changed, 0 insertions, 38 deletions
diff --git a/devel/rubygem-webpacker4-rails50/Makefile b/devel/rubygem-webpacker4-rails50/Makefile deleted file mode 100644 index c818eed87e40..000000000000 --- a/devel/rubygem-webpacker4-rails50/Makefile +++ /dev/null @@ -1,26 +0,0 @@ -PORTNAME= webpacker -PORTVERSION= 4.3.0 -CATEGORIES= devel rubygems -MASTER_SITES= RG -PKGNAMESUFFIX= 4-rails50 - -MAINTAINER= sunpoet@FreeBSD.org -COMMENT= Use Webpack to manage app-like JavaScript modules in Rails - -LICENSE= MIT -LICENSE_FILE= ${WRKSRC}/MIT-LICENSE - -RUN_DEPENDS= rubygem-activesupport50>=4.2:devel/rubygem-activesupport50 \ - rubygem-rack-proxy>=0.6.1:www/rubygem-rack-proxy \ - rubygem-railties50>=4.2:www/rubygem-railties50 \ - yarn:www/yarn - -USES= gem -USE_RUBY= yes - -NO_ARCH= yes - -# webpacker 5.0.0+ requires Rails 5.2.0+ -PORTSCOUT= limit:^4\. - -.include <bsd.port.mk> diff --git a/devel/rubygem-webpacker4-rails50/distinfo b/devel/rubygem-webpacker4-rails50/distinfo deleted file mode 100644 index 7ce03209bdfe..000000000000 --- a/devel/rubygem-webpacker4-rails50/distinfo +++ /dev/null @@ -1,3 +0,0 @@ -TIMESTAMP = 1598029561 -SHA256 (rubygem/webpacker-4.3.0.gem) = 999862bf5a8dea08602f1da26806b142908be3399bdeda5622a42788422d20ba -SIZE (rubygem/webpacker-4.3.0.gem) = 225280 diff --git a/devel/rubygem-webpacker4-rails50/pkg-descr b/devel/rubygem-webpacker4-rails50/pkg-descr deleted file mode 100644 index 0910de7ca8db..000000000000 --- a/devel/rubygem-webpacker4-rails50/pkg-descr +++ /dev/null @@ -1,9 +0,0 @@ -Webpacker makes it easy to use the JavaScript preprocessor and bundler Webpack -to manage application-like JavaScript in Rails. It coexists with the asset -pipeline, as the primary purpose for Webpack is app-like JavaScript, not images, -css, or even JavaScript Sprinkles (that all continues to live in app/assets). It -is, however, possible to use Webpacker for CSS and images assets as well, in -which case you may not even need the asset pipeline. This is mostly relevant -when exclusively using component-based JavaScript frameworks. - -WWW: https://github.com/rails/webpacker |