All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Francis <alistair23@gmail.com>
To: Tim Orling <ticotimo@gmail.com>
Cc: Alistair Francis <alistair@alistair23.me>,
	openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] meta-python: Initial commit of Python3 OBDII module
Date: Thu, 28 Mar 2019 22:09:04 -0700	[thread overview]
Message-ID: <CAKmqyKPVFE2MY+axxm9fJwpT+Eoc=OAvYRcgvzAfg7g6UQss0w@mail.gmail.com> (raw)
In-Reply-To: <CANx9H-BkM_B=C14448U_+yOLPEVwBCVYCa-uX-ENY+XnThLQGw@mail.gmail.com>

On Thu, Mar 28, 2019 at 10:04 PM Tim Orling <ticotimo@gmail.com> wrote:
>
>
>
> On Thu, Mar 28, 2019 at 9:50 PM Alistair Francis <alistair23@gmail.com> wrote:
>>
>> Signed-off-by: Alistair Francis <alistair@alistair23.me>
>> ---
>>  meta-python/recipes-devtools/python/python-obd.inc       | 9 +++++++++
>>  meta-python/recipes-devtools/python/python3-obd_0.7.0.bb | 2 ++
>
>
> Latest version. Ack.

Thanks

>
>>
>>  2 files changed, 11 insertions(+)
>>  create mode 100644 meta-python/recipes-devtools/python/python-obd.inc
>>  create mode 100644 meta-python/recipes-devtools/python/python3-obd_0.7.0.bb
>>
>> diff --git a/meta-python/recipes-devtools/python/python-obd.inc b/meta-python/recipes-devtools/python/python-obd.inc
>> new file mode 100644
>> index 000000000..f2caf6491
>> --- /dev/null
>> +++ b/meta-python/recipes-devtools/python/python-obd.inc
>> @@ -0,0 +1,9 @@
>> +DESCRIPTION = "A python module for handling realtime sensor data from OBD-II vehicle ports"
>> +HOMEPAGE = "https://github.com/brendan-w/python-OBD"
>> +LICENSE = "GPLv2"
>> +LIC_FILES_CHKSUM = "file://README.rst;md5=2988a5e913eb105fa08011135c4157d4"
>
>
> Readmes tend to change in ways not really useful from license standpoint. Why not just use the LICENSE file provided in the repo? Or is it not included in the tarball?

It's not included in the tarball unfortunately.

>>
>>
>> +
>> +SRC_URI[md5sum] = "93e04f825e13b7ebc97d06b6a6407807"
>> +SRC_URI[sha256sum] = "4b1bac95df2faac571ebf444778e4d736d050d8ed7049023c0fc929a520eba6d"
>> +
>> +inherit pypi
>> diff --git a/meta-python/recipes-devtools/python/python3-obd_0.7.0.bb b/meta-python/recipes-devtools/python/python3-obd_0.7.0.bb
>> new file mode 100644
>> index 000000000..578e38d3a
>> --- /dev/null
>> +++ b/meta-python/recipes-devtools/python/python3-obd_0.7.0.bb
>> @@ -0,0 +1,2 @@
>> +inherit setuptools3
>> +require python-obd.inc
>
>
> A python2 version should be trivial, although we should be moving towards python 3 only... so I am ok with leaving python 2 up to someone who needs it.

It does support Python2, but with less then a year to go of support it
didn't seem worth adding.

Alistair

>
>>
>> --
>> 2.20.1
>>
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel


      reply	other threads:[~2019-03-29  5:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29  4:49 [PATCH] meta-python: Initial commit of Python3 OBDII module Alistair Francis
2019-03-29  5:04 ` Tim Orling
2019-03-29  5:09   ` Alistair Francis [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='CAKmqyKPVFE2MY+axxm9fJwpT+Eoc=OAvYRcgvzAfg7g6UQss0w@mail.gmail.com' \
    --to=alistair23@gmail.com \
    --cc=alistair@alistair23.me \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=ticotimo@gmail.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 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.