From: "akuster" <akuster808@gmail.com>
To: "docs@lists.yoctoproject.org" <docs@lists.yoctoproject.org>
Subject: [RFC] Add recipe-yocto-docs
Date: Sun, 1 Nov 2020 10:40:15 -0800 [thread overview]
Message-ID: <d6cadebf-150f-079a-8a47-bf18220a5bfa@gmail.com> (raw)
Hello,
I just finished creating the ability to build the yocto-doc via a recipe
( Thanks to everyone who helped with the sphinx migration)
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akuster/yocto_docs_recipe
There are several structural decision to me made.
Several of the dependency packages that currently reside in other
layers so those might need to moved in core.
The easy decision is where the yocto-doc recipe should live. I suspect
in meta-yocto.
The ones I am not sure are the ones needed to support sphinx. Do we want
these only as Native? Do we want this sphinx in core?
This may be a gateway to allow including the docs in an SDK image. Add
layer based docs. Create an Docs installer, bitbake-docs, etc.
The recipes most likely need a bit of cleaning up. I did test a native
version of the index.html and that worked fine.
- armin
next reply other threads:[~2020-11-01 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 18:40 akuster [this message]
2020-11-02 8:40 ` [docs] [RFC] Add recipe-yocto-docs Nicolas Dechesne
2020-11-02 14:58 ` akuster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6cadebf-150f-079a-8a47-bf18220a5bfa@gmail.com \
--to=akuster808@gmail.com \
--cc=docs@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox