The name fpm is used by another package manager about fpm HOT 8 CLOSED

I vote for 2 as well. I think the two are sufficiently different, but knowing it's out there we can be conscious to avoid confusion as much as possible.

On a side note, should we use that tool to create our Linux packages?

from fpm.

This is unfortunate, though not surprising.

As the originator of the name, I'm sorry. I should've done better research. :(

My preference is also for 2, because I like the name. However I see issues ahead of us, and it will only be more difficult to rename later. Issues are:

• Confusion
• Conflict (both CLI tools are called fpm)
• Bad look on us as the community, as we are a younger project

On a side note, should we use that tool to create our Linux packages?

Though it sounds like a good idea, now we're really screwed: "So fpm will package fpm for Linux. Wait, which fpm is this? Is it this fpm or the other fpm?". I'm confused already. :)

So I vote for 2., if there is a way to do it.

Let's discuss how we could do it. This would probably mean putting a large disclaimer at the top of our README, saying "This fpm is not the other fpm", or similar. What else?

@jordansissel Do you have any advice for us?

from fpm.

from fpm.

I am in agreement. Good call just reaching out and asking, and thank you @jordansissel for your understanding and encouragement.

from fpm.

The fpm help text gave me an idea for an alternate name.

wwf - working with Fortran

It seems like the naming crises has passed, but I'm just too tickled by the idea of scientists and engineers co-opting "WWF" to mean their package manager.

from fpm.

Jordan, thanks a lot. With your encouragement I now feel more comfortable keeping the name, and making it clear in the README to avoid confusion.

So if @certik and @everythingfunctional agree, we'll add the clarification and link to the top of the README.

from fpm.

@jordansissel thank you for your nice comment. Since you are ok with us keeping the name, I am too. @milancurcic yes, let's send a PR with a clarification at the top of our README and docs. That should make it clear to users.

I agree with Jordan that there are ways around it. For example Debian has the alternatives system, so users will be able to choose what they want to run as fpm.

from fpm.

Here is an example how Spack disambiguates the name:

https://spack.readthedocs.io/en/latest/

They write:

These are docs for the Spack package manager. For sphere packing, see pyspack.

from fpm.