Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2011-08-13 | Fix dependency pattern. | taca | 1 | -13/+14 | |
Bump PKGREVISION. | |||||
2010-09-13 | * Add CONFLICTS a pattern matches previous package name | taca | 1 | -1/+3 | |
without "${RUBY_PKGPREFIX}-". | |||||
2010-09-12 | Update www/merb package to 1.1.3. | taca | 3 | -14/+27 | |
* Use lang/ruby/gem.mk instead of misc/rubygems/rubygem.mk. * Add LICENSE. * Ajust new ruby package's framework. * Update dependency according to gemspec. Exact changes are unknown but many. | |||||
2009-06-14 | Convert @exec/@unexec to @pkgdir or drop it. | joerg | 1 | -3/+1 | |
2009-05-16 | Removed references to a non-existent patch-aa file. I wonder how these | rillig | 1 | -2/+1 | |
entries got there. | |||||
2008-04-04 | Initial import of merb-0.9.2 as www/merb. | jlam | 4 | -0/+40 | |
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. In addition, it means that the core code in Merb is kept simple and well organised. This has multiple benefits. It means it's faster for one thing. It's also easier to understand, maintain and extend. |