All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marcin Niestrój" <m.niestroj@grinn-global.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/python-xmodem: new package
Date: Sat, 02 May 2020 12:39:33 +0200	[thread overview]
Message-ID: <87tv0y62oq.fsf@grinn-global.com> (raw)
In-Reply-To: <CALFsTFW=hMQH1sYJEDNPg_=QGeh9iRkMF+m5myR2BE1pv4oGrw@mail.gmail.com>

Hi Asaf,

Asaf Kahlon <asafka7@gmail.com> writes:

> Hello,
>
> On Thu, Apr 30, 2020 at 4:28 PM Marcin Niestr?j
> <m.niestroj@grinn-global.com> wrote:
>>
>> Hi All!
>>
>> The problem with this package is that there is no license file when we
>> download from pypi. But there is one on github. Question is: what should
>> we do about it?
>
> We already have some python packages which don't include the license
> on the tarball, although it exists in the repo.
> Most of the times, it's because the maintainer of the package didn't add
> the license file in MANIFEST.in (which seems to be your case too).
> On those cases, PKG-INFO is mostly used, but it's not the preferred
> solution, so I suggest to send a PR for adding the license to
> MANIFEST.in
> You can see an example from snmpclitools here:
> https://github.com/etingof/snmpclitools/commit/d93597050f7e4708ce875cc47274c39a9e63da11

Thanks for hints! If it takes reasonable time to merge, then I will post
v2 with LICENSE. If not, then I will try PKG-INFO for the time before
next package release.

-- 
Regards,
Marcin Niestr?j

      reply	other threads:[~2020-05-02 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 13:20 [Buildroot] [PATCH] package/python-xmodem: new package Marcin Niestroj
2020-04-30 13:28 ` Marcin Niestrój
2020-05-02  7:54   ` Asaf Kahlon
2020-05-02 10:39     ` Marcin Niestrój [this message]

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=87tv0y62oq.fsf@grinn-global.com \
    --to=m.niestroj@grinn-global.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.