#gemspec — Public Fediverse posts

Hm. #Lazyweb, how do I override the gemspec of a gem?

I am trying to push all gems needed for my Jekyll build to my own #forgejo instance (as a kind of cache), so I get them all with `bundle package`, then try to push them to my forgejo with

`gem push --host https://forge.wildeboer.net/api/packages/<user>/rubygems <GEM>`

But some fail with:

ERROR: "https://forge.wildeboer.net/api/packages/<user>/rubygems" is not allowed by the gemspec, which only allows "https://rubygems.org"

How can I override that?

#Ruby #Gem #Gemspec

Hm. #Lazyweb, how do I override the gemspec of a gem?

I am trying to push all gems needed for my Jekyll build to my own #forgejo instance (as a kind of cache), so I get them all with `bundle package`, then try to push them to my forgejo with

`gem push --host https://forge.wildeboer.net/api/packages/<user>/rubygems <GEM>`

But some fail with:

ERROR: "https://forge.wildeboer.net/api/packages/<user>/rubygems" is not allowed by the gemspec, which only allows "https://rubygems.org"

How can I override that?

#Ruby #Gem #Gemspec

Hm. #Lazyweb, how do I override the gemspec of a gem?

I am trying to push all gems needed for my Jekyll build to my own #forgejo instance (as a kind of cache), so I get them all with `bundle package`, then try to push them to my forgejo with

`gem push --host https://forge.wildeboer.net/api/packages/<user>/rubygems <GEM>`

But some fail with:

ERROR: "https://forge.wildeboer.net/api/packages/<user>/rubygems" is not allowed by the gemspec, which only allows "https://rubygems.org"

How can I override that?

#Ruby #Gem #Gemspec

Hm. #Lazyweb, how do I override the gemspec of a gem?

I am trying to push all gems needed for my Jekyll build to my own #forgejo instance (as a kind of cache), so I get them all with `bundle package`, then try to push them to my forgejo with

`gem push --host https://forge.wildeboer.net/api/packages/<user>/rubygems <GEM>`

But some fail with:

ERROR: "https://forge.wildeboer.net/api/packages/<user>/rubygems" is not allowed by the gemspec, which only allows "https://rubygems.org"

How can I override that?

#Ruby #Gem #Gemspec

Does anyone know how to update the description of a gem on rubygems.org?

I thought it was supposed to be set from the gemspec, but changing that doesn’t seem to have made a difference.

#ruby #rubygems #gemspec

Does anyone know how to update the description of a gem on rubygems.org?

I thought it was supposed to be set from the gemspec, but changing that doesn’t seem to have made a difference.

#ruby #rubygems #gemspec

Does anyone know how to update the description of a gem on rubygems.org?

I thought it was supposed to be set from the gemspec, but changing that doesn’t seem to have made a difference.

#ruby #rubygems #gemspec

Does anyone know how to update the description of a gem on rubygems.org?

I thought it was supposed to be set from the gemspec, but changing that doesn’t seem to have made a difference.

#ruby #rubygems #gemspec

Does anyone know how to update the description of a gem on rubygems.org?

I thought it was supposed to be set from the gemspec, but changing that doesn’t seem to have made a difference.

#ruby #rubygems #gemspec

@cam +1 for not enabling the Gemspec/AddRuntimeDependency rule by default. A #Gemspec doesn't have the same rich grammar as a #Bundler #Gemfile, so by definition anything not a development dependency is a runtime dependency. There's no need to be needlessly verbose about it, so kudos on that choice! 👏

@cam +1 for not enabling the Gemspec/AddRuntimeDependency rule by default. A #Gemspec doesn't have the same rich grammar as a #Bundler #Gemfile, so by definition anything not a development dependency is a runtime dependency. There's no need to be needlessly verbose about it, so kudos on that choice! 👏

@cam +1 for not enabling the Gemspec/AddRuntimeDependency rule by default. A #Gemspec doesn't have the same rich grammar as a #Bundler #Gemfile, so by definition anything not a development dependency is a runtime dependency. There's no need to be needlessly verbose about it, so kudos on that choice! 👏

@cam +1 for not enabling the Gemspec/AddRuntimeDependency rule by default. A #Gemspec doesn't have the same rich grammar as a #Bundler #Gemfile, so by definition anything not a development dependency is a runtime dependency. There's no need to be needlessly verbose about it, so kudos on that choice! 👏

@cam +1 for not enabling the Gemspec/AddRuntimeDependency rule by default. A #Gemspec doesn't have the same rich grammar as a #Bundler #Gemfile, so by definition anything not a development dependency is a runtime dependency. There's no need to be needlessly verbose about it, so kudos on that choice! 👏

Was surprised the gemspec documentation finally switched from `add_dependency` to `add_runtime_dependency`.
https://guides.rubygems.org/specification-reference/
#ruby #gemspec #docs