Open mcanouil opened 1 week ago
Just a note for clarity that quarto update extension
does work, but you need to know the github repo name
> quarto update extension quarto-ext/quarto-poster
and we don't record it for now and we do store the extension in org-name/ext-name
, ext-name
being the registered name from the metadata of the extension. This name is also the one to use inside the document to load a filter for example. filter: [quarto-ext/poster]
So we need to
Find where to store the source information, and maybe other information.
We could adopt an approach similar to R package that does modify the DESCRIPTION in the installed package folder. We could write some fields in the _extension.yml
with install datetime, type of extension (local zip, remote, ...) and source of the remote if so.
Show this information in quarto list extension
indeed
Adapt quarto update
to use the source when installed extension is used (quarto update quarto-ext/poster
) and probably allow to update from source directly quarto update extension quarto-ext/typst-template/poster
Thanks a lot for the report @mcanouil !
Currently, when installation an extension from GitHub, if the extension name does not match the repository name, it's not possible to use
quarto update extension ...
.The majority of extensions uses
quarto-<extension name>
as a repository name instead of<extension name>
. For example:Install extensions:
Check the installed extensions
Update the extensions
This means that it's not possible to update the extension
quarto-ext/poster
because the repository name (directory) istypst-templates/poster
and notposter
. Same goes for the extensionmcanouil/iconify
.This could be solved by recording/keeping the repository name (source) somewhere. It could be in
_extension.yml
undersource
key.Keeping the source would allow better extension management and easier updates, e.g.,
quarto update extension all
.