Archlinux: unable to load tcltk on installation

[iacchus]

When I issued R> install.packages('knitr')

Solution here: rstudio/shiny#52

[Lucas-C]

Could you explain a little bit more your issue here ?
With what plugin do you encounter this issue ? In what context do you issue this R command, and what is the link with this repo ?

[iacchus]

I use Archlinux. When installing your plugin following your instructions I've got the error in R console:

unable to load tcltk on installation

Archlinux users need to install the tk with the command

sudo pacman -S tk

Before doing

R> install.packages('knitr')

edit: sorry, the plugin is rmd_reader

edit 2: As well, wouldn't be better if we had a repo for each plugin or theme? because we have to download each plugin manually and the repositories (plugins and themes) are getting big. But this is another issue.

edit 3: maybe they could be namespaced like for example github.com/getpelican/pelican-plugin-rmd_reader or github.com/getpelican/pelican-theme-attila and to have an instruction to get them like e.g.:

cd [pelican_root]/plugins
git clone github.com/getpelican/pelican-plugin-rmd_reader rmd_reader

Just an idea. :)

edit 4: This would even make possible to install a theme or plugin via a command, then pelican cli would read e.g., PLUGIN_PATHS list and split the the namespace github../etc../pelican-plugin-NAME and to ´git clone´ with NAME that plugin automatically, the user only needing to install it in pelican.conf.

[Lucas-C]

Thanks for the in-depth explanation.

Maybe you could submit a PR to add to rmd_reader/README.md a mention about the issue you faced and the workaround you found ?

About having a repo for each plugin, this is always a possibility. This repo, pelican-plugins, gather efforts to maintain a collection of "community suported" plugins. @wilsonfreitas initiated the rmd_reader plugin in 2014, and other people contributed to it since. It is still possible to extract it in a dedicated repo, and publish it on Pypi, but that would also have its downsides. @wilsonfreitas maybe you have an opinion about it ?

[wilsonfreitas]

The problem relies on knitr, it has many dependencies not directly related to R and it is handled differently among OSs. I developed this plugin using MacOS and I know from others that it runs on Windows and Ubuntu.
I'm not sure that having a separate repo will solve this problem, but I see your point. We might have an opportunity here.
For now, agree with @Lucas-C, an update to README.md would help on this subject.

[justinmayer]

wouldn't be better if we had a repo for each plugin or theme? because we have to download each plugin manually and the repositories (plugins and themes) are getting big.

That is already planned. It's just a question of finding the time to move that effort forward.

It is still possible to extract it in a dedicated repo, and publish it on PyPI, but that would also have its downsides.

If there are concerns with the above-mentioned plan, please feel free to express them in the relevant issue linked above.

[Lucas-C]

@iacchus Do the comments above answer your initial questions / request ?
Do you plan to help on this subject, or maybe else can this issue be closed ?