From: "hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "hsbt (Hiroshi SHIBATA)" <noreply@ruby-lang.org>
Subject: [ruby-core:117225] [Ruby master Feature#20347] Separate docs task from all
Date: Tue, 19 Mar 2024 09:10:29 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-20347.20240319091029.572@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20347.20240319091029.572@ruby-lang.org
Issue #20347 has been reported by hsbt (Hiroshi SHIBATA).
----------------------------------------
Feature #20347: Separate docs task from all
https://bugs.ruby-lang.org/issues/20347
* Author: hsbt (Hiroshi SHIBATA)
* Status: Assigned
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
I would like to migrate RDoc as bundled gems at Ruby 3.5.
We need to handle `install-doc` and related task with that. I removed `docs` task from `all` and re-order `docs` task at `install-all`.
https://github.com/ruby/ruby/pull/10282
It works with RDoc as bundled gems. We can keep current behavior with this migration.
I hope to merge changes for `all` task and re-order `install-all` task at Ruby 3.4.
https://github.com/ruby/ruby/pull/10282/commits/b160083175aed062c320b8d76eafe1c8706309d4
After that, the default `make` task will not generate rdoc. We need to add `make all docs` for that.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/
next parent reply other threads:[~2024-03-19 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 9:10 hsbt (Hiroshi SHIBATA) via ruby-core [this message]
2024-04-17 9:29 ` [ruby-core:117553] [Ruby master Feature#20347] Separate docs task from all hsbt (Hiroshi SHIBATA) via ruby-core
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-20347.20240319091029.572@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=noreply@ruby-lang.org \
--cc=ruby-core@ml.ruby-lang.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).