<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 27/12/22 3:47 PM, Israel Galadima
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAFgEVL7zbRFkAPivkULP-ouHDaRk0ZYPJPhVLOyaJhe62pdrJA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">
          <div dir="ltr">
            <div dir="ltr">
              <div dir="ltr">
                <div dir="ltr">Hi,
                  <div><br>
                  </div>
                  <div>I've found that the upstream author for @unicode
                    packages uses node-unicode-data to generate the
                    unicode data for all <a class="gmail_plusreply"
                      id="gmail-plusReplyChip-1" moz-do-not-send="true">@unicode
                      packages.</a></div>
                  <div><a class="gmail_plusreply" moz-do-not-send="true"><br>
                    </a></div>
                  <div>I was thinking that we could replace all current
                    and future @unicode packages with node-unicode-data
                    instead of having separate packages for them.</div>
                  <div><br>
                  </div>
                  <div>The workflow I am proposing is that we pass the
                    unicode version as a parameter to node-unicode-data
                    and it will download and generate the unicode data
                    for that version.</div>
                  <div><br>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    Ideally we should be able to get these using watch file/uscan. I'm
    not commenting on the suitability of the whole approach (my comment
    is limited to getting orig.tar part), lets see if others have any
    comments.<br>
    <blockquote type="cite"
cite="mid:CAFgEVL7zbRFkAPivkULP-ouHDaRk0ZYPJPhVLOyaJhe62pdrJA@mail.gmail.com">
      <div dir="ltr">
        <div dir="ltr">
          <div dir="ltr">
            <div dir="ltr">
              <div dir="ltr">
                <div dir="ltr">
                  <div>node-unicode-data is not a published npm package
                    so here is the git repo:<br>
                    <a
                      href="https://github.com/node-unicode/node-unicode-data"
                      moz-do-not-send="true"
                      class="moz-txt-link-freetext">https://github.com/node-unicode/node-unicode-data</a>. @unicode
                    packages are only used as build dependencies.<br>
                  </div>
                  <div><br>
                  </div>
                  <div>I'd be happy to work on the package if the
                    suggestion is agreed upon.</div>
                  <div><br>
                  </div>
                  <div>Regards.</div>
                  <div><a class="gmail_plusreply" moz-do-not-send="true"><br>
                    </a></div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
    </blockquote>
  </body>
</html>