search

pandoc-extras / pandocpm

Manage the install/update/uninstall of packages
https://pandoc-extras.github.io/pandocpm/
Apache License 2.0
7 stars 0 forks source link

Package name #1

Closed sergiocorreia closed 7 years ago

sergiocorreia commented 7 years ago

Not sure what name to pick

ickc commented 7 years ago

you mean the name of pandocpm?

Brain-storming:

checked are my favorites. pacdoc might works better as a package manager while panfill might fit better as an organization name.

sergiocorreia commented 7 years ago

I'm fine with both, and also with pandocpm. Maybe we can also ask the folks at the google group...

ickc commented 7 years ago

After letting it sink for a few days, I think I prefer pacdoc the best. It is catchy and easy to type. For things like tlmgr, every time I type that I was saying "TeX Live Manager" in my mind, which makes it slower to type. What do you think?

ickc commented 7 years ago

Ah, I see that @sergiocorreia already setup pandocpm, so renaming can be a problem.

And by the way, can @sergiocorreia add the pypi password in Travis CI in the same way did in panflute? Then I can setup Travis to push to there.

sergiocorreia commented 7 years ago

Done. About the renaming, it can be done (just rename repo and delete pypi package), but my only concern is that people would type "packdoc" instead of "pacdoc" (unless maybe if you have arch linux and use pacman)

ickc commented 7 years ago

About the travis deploy, since it is built from my travis, and my travis don't have your password, it doesn't work.

A proper way to do it would be add me as maintainer in PyPI's pandocpm, then I can use my own PyPI password in my Travis.

But we should do that after we finalized the name though.

Another name popped up in my mind a few hours ago is something like papm stands for "papm ain't package manager". Kind of old tricks, but emphasize that it ain't managing the versions for example. One thing I worry about the name pandocpm is it might set the expectation higher than what we build it for.

Edit: typo

sergiocorreia commented 7 years ago

About the travis deploy, since it is built from my travis, and my travis don't have your password, it doesn't work.

BTW, I just added the pypi_password env variable to my TravisCI for the project, so it should work as with e.g. panflute

ickc commented 7 years ago

BTW, I just added the pypi_password env variable to my TravisCI for the project, so it should work as with e.g. panflute

Right, the Travis is actually pandoc-extras, not ickc's, so it should work.

It almost work, but

HTTPError: 401 Client Error: You must be identified to edit package information for url: https://pypi.python.org/pypi

I don't know what's going on.

ickc commented 7 years ago

Ah, I know it now. Fixed Travis config in bb067cb.

ickc commented 7 years ago

@sergiocorreia About the package name: I guess no one really cares which exact name to use. So I'll let you decide which one you like most and we can stick with it.

sergiocorreia commented 7 years ago

I would just leave it as it is. I'm a bit short of time these days (holidays, work, etc) but I'll try to push an update on the most important features after that.

ickc commented 7 years ago

Sure. Let's close this issue then.

When I have time, I will try to read through and see what I can do too. The "deadline" I was having is about mid-Jan, before next semester starts, for collaborations between GSIs to edit a workbook. But now that project becomes dormant due to budget issue, so I don't have such deadline anymore.