You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regarding the symbol that goes into pkgs.janet, should it be the same as the :name value in the project's declare-project (in the project's project.janet file)?
The contributing doc says, "One exception is the janet- prefix in the git repository name to avoid name clashes.", but does not explain the meaning. I think what it means to say is, if your git repo name includes the "janet-" prefix, don't include that in the project name. Is that correct?
The text was updated successfully, but these errors were encountered:
Re. # 1 above, does jpm use the symbol in pkgs.janet for anything other than an alias to the git repo? That is to say, does jpm care if the symbol in pkgs.janet is different from the project's own "project.janet --> declare-project --> :name" value?
Yes, the naming is really more about keeping consistency. As far as what jpm uses the names for, yes they are aliases to git repos. They are more important than the :name field in a declare project as far as jpm is concerned.
So, when jpm is installing a bare package name (not fully-qualified url), it just looks up that bare name in the pkgs.janet and uses it as an alias to the git repo.
But once it does that, it then uses the :name in that project's project.janet --> declare-project to ... is that just used to name the /usr/local/lib/janet subdir name? What does jpm use the :name value for?
Two things I think need to be clarified:
Regarding the symbol that goes into pkgs.janet, should it be the same as the
:name
value in the project'sdeclare-project
(in the project's project.janet file)?The contributing doc says, "One exception is the janet- prefix in the git repository name to avoid name clashes.", but does not explain the meaning. I think what it means to say is, if your git repo name includes the "janet-" prefix, don't include that in the project name. Is that correct?
The text was updated successfully, but these errors were encountered: