All of lore.kernel.org
 help / color / mirror / Atom feed
From: "akuster" <akuster808@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>, Adrian Bunk <bunk@stusta.de>
Cc: OpenEmbedded Development mailing list
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] standardizing HOMEPAGE values in python3 recipes
Date: Tue, 16 Jun 2020 15:11:19 -0700	[thread overview]
Message-ID: <f5d64627-7b4a-94df-d487-e578cd62fc41@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2006161807070.7432@localhost.localdomain>

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



On 6/16/20 3:08 PM, Robert P. J. Day wrote:
> On Tue, 16 Jun 2020, Adrian Bunk wrote:
>
>> On Tue, Jun 16, 2020 at 06:36:50AM -0400, Robert P. J. Day wrote:
>>>   given the current flurry of python recipe cleanup, just want to
>>> verify a couple things that could/should be standardized.
>>>
>>>   first, HOMEPAGE values of the form:
>>>
>>>   https://pypi.python.org/pypi/astroid
>>>
>>> can be adjusted to reflect the result of the redirection, as in:
>>>
>>>   https://pypi.org/project/astroid
>>>
>>> also, as i read it, recipe HOMEPAGE values should *not* refer to the
>>> pypi page, as that is already set automatically by pypi.bbclass.
>>> rather, the HOMEPAGE should refer to the actual source home page,
>>> which in the case of the astroid package would be:
>>>
>>>   https://github.com/PyCQA/astroid
>>>
>>> does this make sense?
>> When the source is on github this is supposed to be linked from
>> PyPi.
>>
>> My personal impression is that meta data like the HOMEPAGE field is
>> usually poorly maintained, keeping an automatically set "good
>> enough" value (the PyPi link) would IMHO be the best default option.
>   i'm inclined to agree, but i will at least lay down some standards
> for a few people as to how to craft recipes from now on.

Beyond: http://www.openembedded.org/wiki/Styleguide ?
>
> rday
>
> 


[-- Attachment #2: Type: text/html, Size: 2617 bytes --]

  reply	other threads:[~2020-06-16 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 10:36 standardizing HOMEPAGE values in python3 recipes Robert P. J. Day
2020-06-16 19:43 ` [oe] " Adrian Bunk
2020-06-16 22:08   ` Robert P. J. Day
2020-06-16 22:11     ` akuster [this message]
2020-06-19  0:05 ` Khem Raj

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=f5d64627-7b4a-94df-d487-e578cd62fc41@gmail.com \
    --to=akuster808@gmail.com \
    --cc=bunk@stusta.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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.