Bug#1103848: ruby-rails-propshaft: package name should be ruby-propshaft

2025-04-23 Thread Antonio Terceiro
On Wed, Apr 23, 2025 at 02:12:32PM +0530, Pirate Praveen wrote: > > On 23/04/2025 1:49 pm, Soren Stoutner wrote: > > The thought process with the name is that this package is only useful > > to rails. It can’t be used generally by other Ruby packages. > > > > Upstream is propshaft inside of the

Bug#1103848: ruby-rails-propshaft: package name should be ruby-propshaft

2025-04-23 Thread Pirate Praveen
On 23/04/2025 1:49 pm, Soren Stoutner wrote: The thought process with the name is that this package is only useful to rails. It can’t be used generally by other Ruby packages. Upstream is propshaft inside of the rails project. Only golang follows that convention because you have to also impo

Bug#1103848: ruby-rails-propshaft: package name should be ruby-propshaft

2025-04-23 Thread Soren Stoutner
The thought process with the name is that this package is only useful to rails. It can’t be used generally by other Ruby packages. Upstream is propshaft inside of the rails project. https://github.com/rails/propshaft However, if there is a general consensus that this should be named ruby-prop

Bug#1103848: ruby-rails-propshaft: package name should be ruby-propshaft

2025-04-21 Thread Pirate Praveen
Package: ruby-rails-propshaft Version: 1.1.0-3 Severity: important X-Debbugs-Cc: prav...@debian.org Dear Maintainer, Usually all rubygems get a ruby-prefixed to the gem name. Any reason to deviate from the standard? I think it'd be better if this package also followed the standard practice of ru