cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
92d2729a69
openbsd-ports/www/ruby-merb/assets/Makefile

11 lines
258 B
Makefile
Raw Normal View History

REVISION bump all ruby ports due to a change in the pkgspec. Previously, we were using ruby->=1.8,<=1.9, instead of ruby->=1.8,<1.9. While this wouldn't cause an issue, since our ruby-1.9.2 package isn't included in ruby->=1.8,<=1.9, it's still wrong and should be fixed. This also fixes the following minor issues: Switch from using FLAVOR to MODRUBY_FLAVOR for *_DEPENDS. Currently we don't have a ruby port that uses FLAVORs that would differ from MODRUBY_FLAVOR, but it's possible we will in the future. Switch from BASE_PKGPATH to BUILD_PKGPATH in a few cases in REGRESS_DEPENDS. This probably is not strictly necessary, but BUILD_PKGPATH is used in more cases, so it is good for consistency. Switch to new style *_DEPENDS, with the version specification at the end. The remaining cases where this is not done is because a specific version is used. Some FULLPKGNAME added to REGRESS_DEPENDS, to make sure that if the old version is installed when you run a regress test, it will install the new version first. Some conversion of spaces to tabs for consistency. OK landry@
2010-11-24 16:35:13 -05:00
# $OpenBSD: Makefile,v 1.9 2010/11/24 21:35:16 jeremy Exp $
Initial import of ruby-merb-0.9.2. Like Ruby on Rails, Merb is an MVC framework. Unlike Rails, Merb is ORM-agnostic, JavaScript library agnostic, and template language agnostic, preferring plugins that add in support for a particular feature rather than trying to produce a monolithic library with everything in the core. In fact, this is a guiding principle of the project, which has led to third-party support for the ActiveRecord, DataMapper, and Sequel ORMs.
2008-04-19 17:57:18 -04:00
Update the Merb framework to 1.0.8.1.
2009-01-31 07:40:06 -05:00
COMMENT = provide Merb helpers for assets and asset bundling
Initial import of ruby-merb-0.9.2. Like Ruby on Rails, Merb is an MVC framework. Unlike Rails, Merb is ORM-agnostic, JavaScript library agnostic, and template language agnostic, preferring plugins that add in support for a particular feature rather than trying to produce a monolithic library with everything in the core. In fact, this is a guiding principle of the project, which has led to third-party support for the ActiveRecord, DataMapper, and Sequel ORMs.
2008-04-19 17:57:18 -04:00
Update the Merb framework to 1.0.8.1.
2009-01-31 07:40:06 -05:00
DISTNAME = merb-assets-${VERSION}
REVISION bump all ruby ports due to a change in the pkgspec. Previously, we were using ruby->=1.8,<=1.9, instead of ruby->=1.8,<1.9. While this wouldn't cause an issue, since our ruby-1.9.2 package isn't included in ruby->=1.8,<=1.9, it's still wrong and should be fixed. This also fixes the following minor issues: Switch from using FLAVOR to MODRUBY_FLAVOR for *_DEPENDS. Currently we don't have a ruby port that uses FLAVORs that would differ from MODRUBY_FLAVOR, but it's possible we will in the future. Switch from BASE_PKGPATH to BUILD_PKGPATH in a few cases in REGRESS_DEPENDS. This probably is not strictly necessary, but BUILD_PKGPATH is used in more cases, so it is good for consistency. Switch to new style *_DEPENDS, with the version specification at the end. The remaining cases where this is not done is because a specific version is used. Some FULLPKGNAME added to REGRESS_DEPENDS, to make sure that if the old version is installed when you run a regress test, it will install the new version first. Some conversion of spaces to tabs for consistency. OK landry@
2010-11-24 16:35:13 -05:00
REVISION = 2
Initial import of ruby-merb-0.9.2. Like Ruby on Rails, Merb is an MVC framework. Unlike Rails, Merb is ORM-agnostic, JavaScript library agnostic, and template language agnostic, preferring plugins that add in support for a particular feature rather than trying to produce a monolithic library with everything in the core. In fact, this is a guiding principle of the project, which has led to third-party support for the ActiveRecord, DataMapper, and Sequel ORMs.
2008-04-19 17:57:18 -04:00
REVISION bump all ruby ports due to a change in the pkgspec. Previously, we were using ruby->=1.8,<=1.9, instead of ruby->=1.8,<1.9. While this wouldn't cause an issue, since our ruby-1.9.2 package isn't included in ruby->=1.8,<=1.9, it's still wrong and should be fixed. This also fixes the following minor issues: Switch from using FLAVOR to MODRUBY_FLAVOR for *_DEPENDS. Currently we don't have a ruby port that uses FLAVORs that would differ from MODRUBY_FLAVOR, but it's possible we will in the future. Switch from BASE_PKGPATH to BUILD_PKGPATH in a few cases in REGRESS_DEPENDS. This probably is not strictly necessary, but BUILD_PKGPATH is used in more cases, so it is good for consistency. Switch to new style *_DEPENDS, with the version specification at the end. The remaining cases where this is not done is because a specific version is used. Some FULLPKGNAME added to REGRESS_DEPENDS, to make sure that if the old version is installed when you run a regress test, it will install the new version first. Some conversion of spaces to tabs for consistency. OK landry@
2010-11-24 16:35:13 -05:00
RUN_DEPENDS = www/ruby-merb/core,${MODRUBY_FLAVOR}>=${VERSION}
Initial import of ruby-merb-0.9.2. Like Ruby on Rails, Merb is an MVC framework. Unlike Rails, Merb is ORM-agnostic, JavaScript library agnostic, and template language agnostic, preferring plugins that add in support for a particular feature rather than trying to produce a monolithic library with everything in the core. In fact, this is a guiding principle of the project, which has led to third-party support for the ActiveRecord, DataMapper, and Sequel ORMs.
2008-04-19 17:57:18 -04:00
.include <bsd.port.mk>
Reference in New Issue Copy Permalink