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 rails project.
> 
> Only golang follows that convention because you have to also import by full
> url. But every rubygem the name is unique and every other ruby gem package
> only adds ruby- to gem name. Only when there is fork and two different gems
> by close enough gems we add the repo name.
> 
> This is already established naming standard used for all rubygems as
> codified in gem2deb.
> 
> > https://github.com/rails/propshaft
> > 
> > However, if there is a general consensus that this should be named
> > ruby-propshaft I am not opposed to changing it.

AFAICT there is no strictly technical reason to name it ruby-propshaft,
but following the established convention makes it simpler for us humans.

Attachment: signature.asc
Description: PGP signature

Reply via email to