Re: [NonGNU ELPA] New package: project-store
Philip Kaludercic <[email protected]>
| Newsgroups | gmane.emacs.devel |
|---|---|
| Message-ID | <[email protected]> |
Lin Jian <[email protected]> writes: > Philip Kaludercic <[email protected]> writes: > >> You are right that we don't want to reject a name just based on a >> package (except if the package name were something vulgar or vague), but >> we never said that we'll at least not _try_ to change your mind and/or >> find a compromise if we think that there is a good reason to ;) > > Agree. And "your preferences are acknowledged". > >> Stéphane did raise good points that -- regardless of where the package >> is hosted -- indicate that it would be better to use a less generic >> name. > > His suggestions and arguments do not align with each other, which makes > them hard to understand and reason. > > After he put words in my mouth, (I think) I finally get his reasoning: > > 1. He tries to not use "store" to refer to something generic than > Nix/Guix/... store. (This is reasonable by itself.) > 2. Due to 1, he tries to avoid using "store" in my package name. > (While he arguing for this, he seems to try to hide 1 for some > reason.) > > The connection between 1 and 2 is interesting because my package only > focuses on Nix/Guix/... store, nothing more generic. > > At this point, I have to conclude it won't be of any good to continue > discussion with him on this topic. > > (BTW, I do not think his suggestions are less generic. Is project-nix > less generic than project-store?) I'd say so, since "nix" is not an English word but a name, and "store" is both a noun and a verb. >> Just to know: Is there a rush in publishing this package, such as an >> upcoming release of Nix where this package would either be added to the >> distribution before some cutoff date? > > No cutoff date. But I do not want to delay publishing this package for > no good reason. > >> If you are thereby saying that you are committing to the name, and don't >> foresee any chance that you'll change your mind, then I guess we might >> as well add the package spec to nongnu.git. > > After all these discussion of name, I have not been convinced to change > it. So yes, I am committing to that name. OK, I have pushed the package to nongnu.git.