Update install instructions #10
Conversation
content/pages/1.install.md
Outdated
|
|
||
| I haven't built an RPM package for mycli yet. So please use `pip` to install `mycli`. You can install pip on your system using: | ||
| We don't have an RPM package for mycli, yet. So, please use `pip` to install `mycli`. You can install pip on your system using: |
There was a problem hiding this comment.
If people are able to install it on Fedora doesn't that mean there is an RPM package for it?
/cc @meeuw
There was a problem hiding this comment.
Good question. Maybe you or @meeuw can help me figure out what better wording for that is.
Is there an easy, non-pip way to install mycli on RHEL or Centos?
If not, is it better to simply say "We don't have packages for RHEL or Centos, yet. So, please use pip..."?
There was a problem hiding this comment.
The RPM can be used on Centos/RHEL but most of the dependencies are missing. I've created a repository with all the dependencies on https://copr.fedorainfracloud.org/coprs/meeuw/mycli-epel/
I'd like to get this into Fedora-EPEL but haven't found the time to do this.
…ll_instructions * 'master' of github.com:dbcli/mycli.net: Remove prompt from sample .my.cnf. Add mysql section note to config docs. Add pager instructions. Add note about editing previous command. Add introduction and headings. Update config and add mysql option file.
|
Hmm, I though I've added a comment this morning, but I don't see it anymore. I'm working on getting the dependencies in EPEL, I've already packaged them: I'm not sure if we should publish it right now. |
|
@meeuw - Thanks for being so thorough. Your comment is there, you have to click on "Show Outdated", though. I reworded the docs in this pull request. Then, whenever it changes in the future, we can update it then. Thanks! |
|
👍 This is fine for now |
content/pages/1.install.md
Outdated
| ### RHEL, Centos, Fedora: | ||
| ### Fedora | ||
|
|
||
| :::bash |
There was a problem hiding this comment.
This triple colon is not rendering properly in md.
Is that intentional?
There was a problem hiding this comment.
Hmm, yeah, I think that's how Pelican does code blocks. Github-flavored Markdown is different.
To be honest, I was imitating the triple-colons that were already in the file. Looking at Pelican's docs, it seem like what they recommend (and when you run the development server, it renders).
|
🦊 |
This: