Issues - fauna/echoe

fauna / echoe

Description:

A Rubygems packaging tool that provides Rake tasks for documentation, extension compiling, testing, and deployment

Sort by: Priority | Votes | Last Updated

Loading…

1.

0 votes

add ability to execute both manifest and install
0 comments Created 7 months ago by coshx

Title

Body
Currently if there's no Manifest, then instantiation fails unless you explicitly run "rake manifest". I would like to be able to do something like the following in my Rakefile: task :my_install => [:manifest, :install] Even if I touch a Manifest file first, I get an error in the following circumstance: 1. create a new file (foo.txt) 2. run "rake manifest" 3. delete the new file 4. run rake my_install expected: gem installs actual: package task balks since it doesn't "know how to build task 'foo.txt'". The workaround (system 'rake manifest') is pretty simple, but isn't the most elegant solution.
or cancel

Currently if there's no Manifest, then instantiation fails unless you explicitly run "rake manifest". I would like to be able to do something like the following in my Rakefile:
task :my_install => [:manifest, :install]

Even if I touch a Manifest file first, I get an error in the following circumstance:
1. create a new file (foo.txt)
2. run "rake manifest"
3. delete the new file
4. run rake my_install

expected: gem installs
actual: package task balks since it doesn't "know how to build task 'foo.txt'".

The workaround (system 'rake manifest') is pretty simple, but isn't the most elegant solution.

Comments

Parsed with GitHub Flavored Markdown
2.

0 votes

There should be a way to override -P MediumSecurity
2 comments Created 2 months ago by coshx

Title

Body
I'm not sure that -P MediumSecurity needs to be part of the gem install command in echoe.rb, since this can be set in ~/.gemrc as a default. At the very least, though, there should be a way to override it. This turned out to be a sticking point when we had, ahem, memcached listed as a dependent gem. I know the correct procedure is to add the appropriate certificates, but this becomes more difficult when we run installs on several machines. Also, it's not always obvious which gem is failing since the error message doesn't contain the name of the gem.
or cancel

I'm not sure that -P MediumSecurity needs to be part of the gem install command in echoe.rb, since this can be set in ~/.gemrc as a default. At the very least, though, there should be a way to override it. This turned out to be a sticking point when we had, ahem, memcached listed as a dependent gem.

I know the correct procedure is to add the appropriate certificates, but this becomes more difficult when we run installs on several machines.

Also, it's not always obvious which gem is failing since the error message doesn't contain the name of the gem.

Comments

fauna Tue Sep 29 14:51:40 -0700 2009 | link

You are running "rake install" via echoe on multiple machines...? I don't quite follow.

Comment
You are running "rake install" via echoe on multiple machines...? I don't quite follow.
or cancel

coshx Tue Sep 29 15:49:38 -0700 2009 | link

yeah, we have internal libraries that we install as gems (and use echoe for building/installing these gems and dealing wtih dependencies). So for example, on our CI server, we have it building all our gems by running "rake install", which pulls in all the dependent gems as well. It's difficult to fit key management into this workflow.

I do understand the security concerns with wanting MediumSecurity, but I think echoe should use the default rubygems setting, which can be overridden by an entry in /etc/gemrc or ~/.gemrc

Comment
yeah, we have internal libraries that we install as gems (and use echoe for building/installing these gems and dealing wtih dependencies). So for example, on our CI server, we have it building all our gems by running "rake install", which pulls in all the dependent gems as well. It's difficult to fit key management into this workflow. I do understand the security concerns with wanting MediumSecurity, but I think echoe should use the default rubygems setting, which can be overridden by an entry in /etc/gemrc or ~/.gemrc
or cancel

Parsed with GitHub Flavored Markdown

Labels

add ability to execute both manifest and install

Comments

There should be a way to override -P MediumSecurity

Comments