Hi Pepjin, to package a buildr extension you typically don't need to use Buildr itself. You can create a .gemspec file, then do:
gem build gem.gemspec gem push gem-1.0.gem I might be missing something, but really the line you point at is not related to gem building and is very important in Buildr - it helps Buildr know how to handle packages as artifacts, so where to upload them for example. Thanks, Antoine On Wed, Feb 10, 2010 at 01:54, Pepijn Van Eeckhoudt <[email protected] > wrote: > Hi, > > I'm trying to package a buildr extension as a gem so I can distribute it > more easily. It seems the PackageGemTask#install method is never called > though. > > I'm kind of new to Ruby so I'm not 100% sure what's going on, but I think > line 173 in buildr/packaging/package.rb ('package.extend ActsAsArtifact') is > to blame. By extending the package object with ActsAsArtifact, the install, > uninstall and upload methods get overridden and so the Gem specific variants > are never invoked. > > I would like to patch this, but I'm not sure what would be the best way > would be to resolve this? Is there some Ruby idiom that would allow this? > > Regards, > > Pepijn Van Eeckhoudt >
