public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] python-license-expression and cygport PoC patch
Date: Thu, 6 Jun 2024 13:28:08 -0600	[thread overview]
Message-ID: <64130d4b-f464-4db4-af9a-23b26dd9701a@SystematicSW.ab.ca> (raw)
In-Reply-To: <d4887188-6196-4257-a83b-e682a83d4ee7@SystematicSW.ab.ca>

On 2024-06-06 13:03, Brian Inglis via Cygwin-apps wrote:
> I found github/nexB/license-expression Python package to do SPDX licence checks 
> developed by the same team doing SPDX-toolkit for SPDX, using the same current 
> data, by and working with Fedora folks et al.
> 
> Successful attempt to package Python license-expression (without tests):
> 
>      https://cygwin.com/cgi-bin2/jobs.cgi?id=8210

https://cygwin.com/cgi-bin2/jobs.cgi?id=8210&srcpkg=playground&user=Brian+Inglis

> log at:
> 
>      https://github.com/cygwin/scallywag/actions/runs/9293093201
> 
> cygport attached and at:
> 
> https://cygwin.com/cgit/cygwin-packages/playground/commit/?id=3626386b10c967f780547d1703ad23bd50f6331a
> 
> The package installs and runs using PoC attached in spdx-license-expression.py 
> script hooked into /usr/share/cygport/lib/pkg_pkg.cygpart license hint addition 
> patch attached.
> 
> I also ran a test of the Python script and module against all package source 
> cygport files declaring licences which I maintain or ever looked at, including a 
> git/cygwin-packages/*.cygport download from 2023-02, showing the results in the 
> attached log.
> I also attempted to trap the exceptions in the script, but that does not seem to 
> work in any documented obvious manner, but I do not know enough Python to 
> address this fully.
> 
> If someone else who knows python cared to adopt and improve this in a more 
> normal manner, and incorporate this more smoothly into cygport, we could all 
> appreciate that.
> Alternatively, some candid comments and frank feedback might allow me to do so! ;^>

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

  reply	other threads:[~2024-06-06 19:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 19:03 Brian Inglis
2024-06-06 19:28 ` Brian Inglis [this message]
2024-06-08 16:04   ` Brian Inglis
2024-06-23 14:26 ` Jon Turney
2024-06-23 20:12   ` Brian Inglis

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=64130d4b-f464-4db4-af9a-23b26dd9701a@SystematicSW.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).