public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Daisuke Fujimura <booleanlabel@gmail.com>
To: cygwin-apps@cygwin.com
Subject: [ITA] ruby-rdoc 6.5.0
Date: Wed, 3 May 2023 13:42:15 +0900	[thread overview]
Message-ID: <CAA3frXRZ6JH6jj9OhU7mxCCsZwmHC0jiPh6Nz88ZWDUsnYQHUQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 489 bytes --]

Hello,

====

Cygportfile:
- https://cygwin.com/cgit/cygwin-packages/playground/tree/?h=ruby-rdoc

Packages:
- https://yacp.osdn.jp/ita/ruby-rdoc/

> Therefore, it is necessary to update rdoc first, but packaging
> rdoc-6.5.0 also fails for the same reason, so it needs to be updated
> by other means besides scallywag:
> - Create a package using ruby-2.6.4.
> - Create a package using rdoc-6.5.0 installed in a different location
> with gem install.

I created a package with the latter.

[-- Attachment #2: ruby-rdoc.diff --]
[-- Type: application/octet-stream, Size: 523 bytes --]

diff --git a/ruby-rdoc.cygport b/ruby-rdoc.cygport
index a2b2226..abe3ec0 100644
--- a/ruby-rdoc.cygport
+++ b/ruby-rdoc.cygport
@@ -1,7 +1,7 @@
 inherit rubygem
 
 NAME="ruby-rdoc"
-VERSION=6.1.2
+VERSION=6.5.0
 RELEASE=1
 CATEGORY="Ruby"
 SUMMARY="Ruby rdoc module"
@@ -9,6 +9,8 @@ DESCRIPTION="RDoc produces HTML and command-line documentation for Ruby
 projects. RDoc includes the rdoc and ri tools for generating and displaying
 online documentation."
 
+LICENSE=Ruby
+
 ARCH=noarch
 
 PKG_NAMES="${NAME} ${NAME}-doc"

             reply	other threads:[~2023-05-03  4:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  4:42 Daisuke Fujimura [this message]
2023-05-04 13:51 ` Jon Turney

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=CAA3frXRZ6JH6jj9OhU7mxCCsZwmHC0jiPh6Nz88ZWDUsnYQHUQ@mail.gmail.com \
    --to=booleanlabel@gmail.com \
    --cc=cygwin-apps@cygwin.com \
    /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).