Dne 27. 06. 22 v 13:21 Benson Muite napsal(a):
Hi Pavel,
Thanks. Is it also worth encouraging packaging of Ri documentation?
These are very comandline friendly, Javascript is not. In principle,
one might want to have HTML documentation as a separate package from
Ri documentation giving the end user a choice of what to install.
Of course that would be nice in ideal world. If I only had a time to
implement this.
Will see if can figure out some way of removing fonts.
There are several options:
1) Keep the status quo,
2) Just drop the fonts and leave the browser to use some substitutes
3) Symlink the system fonts.
I have never experimented with (2) / (3).
Of course ideal would be to have our own template for the RDoc
documentation which could be linked instead the copied version. This
would save us from these issues as well as saved disk space.
Vít
Regards,
Benson
On 6/27/22 13:30, Pavel Valena wrote:
> Hello Benson,
>
> as of now, this hasn't been an issue and I think there's no obstacle
> with using the javascript (the library has reported vulnerability
> AFAIR), but it's not exploitable in the documentation so it's deemed
> safe (the library should not be used for anything else).
>
> The same goes for the font (if it's shipped in the package itself,
> it's probably fine to remove it, or state the license).
>
> HIH,
> Pavel
>
> On Sat, Jun 25, 2022 at 6:35 AM Benson Muite
> <benson_muite(a)emailplus.org <mailto:benson_muite@emailplus.org>> wrote:
>
> Hi,
>
> Rdoc generated HTML often includes embedded fonts and javascript
> which
> may be problematic to package. Might it be worth suggesting in the
> packaging documentation[0] to only create Ri files which are
> accessible
> on the command line? A related ticket that prompted this is [1].
>
> Regards,
> Benson
>
> 0]
https://docs.fedoraproject.org/en-US/packaging-guidelines/Ruby/
> <
https://docs.fedoraproject.org/en-US/packaging-guidelines/Ruby/>
> 1]
https://bugzilla.redhat.com/show_bug.cgi?id=2097267
> <
https://bugzilla.redhat.com/show_bug.cgi?id=2097267>
> _______________________________________________
> ruby-sig mailing list -- ruby-sig(a)lists.fedoraproject.org
> <mailto:ruby-sig@lists.fedoraproject.org>
> To unsubscribe send an email to
> ruby-sig-leave(a)lists.fedoraproject.org
> <mailto:ruby-sig-leave@lists.fedoraproject.org>
> Fedora Code of Conduct:
>
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> <
https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
> List Guidelines:
>
https://fedoraproject.org/wiki/Mailing_list_guidelines
> <
https://fedoraproject.org/wiki/Mailing_list_guidelines>
> List Archives:
>
https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraprojec...
>
<
https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraprojec...
> Do not reply to spam on the list, report it:
>
https://pagure.io/fedora-infrastructure
> <
https://pagure.io/fedora-infrastructure>
>
>
> _______________________________________________
> ruby-sig mailing list -- ruby-sig(a)lists.fedoraproject.org
> To unsubscribe send an email to ruby-sig-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
>
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
>
https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraprojec...
> Do not reply to spam on the list, report it:
>
https://pagure.io/fedora-infrastructure
_______________________________________________
ruby-sig mailing list -- ruby-sig(a)lists.fedoraproject.org
To unsubscribe send an email to ruby-sig-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraprojec...
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure