From: John Snow <jsnow@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: "Cleber Rosa" <crosa@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [qemu.qmp PATCH 04/12] update project URLs
Date: Tue, 26 Apr 2022 12:38:24 -0400 [thread overview]
Message-ID: <CAFn=p-aFu0eHZCWT2acuiQLWeLVHt5gMyqc11TfiM0i3tqwMrA@mail.gmail.com> (raw)
In-Reply-To: <YmeqR3gbsZO9FH4u@paraplu>
On Tue, Apr 26, 2022 at 4:16 AM Kashyap Chamarthy <kchamart@redhat.com> wrote:
>
> On Tue, Apr 26, 2022 at 08:55:38AM +0100, Daniel P. Berrangé wrote:
> > On Mon, Apr 25, 2022 at 02:19:27PM -0400, John Snow wrote:
> > > On Mon, Apr 25, 2022, 6:56 AM Daniel P. Berrangé <berrange@redhat.com>
> > > wrote:
> > >
> > > > On Fri, Apr 22, 2022 at 02:49:32PM -0400, John Snow wrote:
> > > > > Point to this library's URLs instead of the entire project's.
> > > > >
> > > > > Signed-off-by: John Snow <jsnow@redhat.com>
> > > > > ---
> > > > > setup.cfg | 4 ++--
> > > > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > > > >
> > > > > diff --git a/setup.cfg b/setup.cfg
> > > > > index c21f2ce..0a1c215 100644
> > > > > --- a/setup.cfg
> > > > > +++ b/setup.cfg
> > > > > @@ -5,8 +5,8 @@ author = QEMU Project
> > > > > author_email = qemu-devel@nongnu.org
> > > > > maintainer = John Snow
> > > > > maintainer_email = jsnow@redhat.com
> > > > > -url = https://www.qemu.org/
> > > > > -download_url = https://www.qemu.org/download/
> > > > > +url = https://gitlab.com/qemu-project/python-qemu-qmp
> > > > > +download_url =
> > > > https://gitlab.com/qemu-project/python-qemu-qmp/-/packages
> > > >
> > > > Auto-generated tarballs are not guaranteed to have fixed content forever
> > > > so I tend to avoid pointing to those. Assuming you're intending to upload
> > > > to pypi, I'd link to that instead as the "official" tarball source.
> > > >
> > >
> > > This metadata will also be used for PyPI, so that seemed cyclic.
> > >
> > > I linked it to the gitlab package repository, where I *intend* to push
> > > built wheels (and dev interstitial builds) but maybe that's too "inside
> > > baseball" for a pypi link.
> >
> > Oh wait, I mis-understood the URL. If it is the location for manually
> > built & published dists, that's ok - it isn't the gitlab auto tarballs.
> >
> > > Seems weird for a Pypi package to point to itself on pypi, but maybe that's
> > > correct?
> >
> > I wonder what common practice is for some popular python libs....
>
> E.g. if you look at SQLAlchemy (definitely one of the popular
> libraries), it is pointing to itself (see the Ufiles under the "Download
> files" link):
>
> https://pypi.org/project/SQLAlchemy
>
The "Files" link is, I believe, just a standard PyPI link. "Download"
is the one being defined here.
Check out my "Alpha 0" page, generated earlier this year:
https://pypi.org/project/qemu.qmp/
Download Files goes to the PyPI section, but "Download" goes to the
GitLab package registry.
I think I'll leave this as-is, then.
--js
next prev parent reply other threads:[~2022-04-26 17:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 18:49 [qemu.qmp PATCH 00/12] python: fork qemu.qmp python lib into independent repo John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 01/12] fork qemu.qmp from qemu.git John Snow
2022-04-25 10:37 ` Daniel P. Berrangé
2022-04-25 18:54 ` John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 02/12] update maintainer metadata John Snow
2022-04-25 10:54 ` Daniel P. Berrangé
2022-04-25 18:15 ` John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 03/12] update project description John Snow
2022-04-29 13:44 ` Beraldo Leal
2022-04-22 18:49 ` [qemu.qmp PATCH 04/12] update project URLs John Snow
2022-04-25 10:56 ` Daniel P. Berrangé
2022-04-25 18:19 ` John Snow
2022-04-26 7:55 ` Daniel P. Berrangé
2022-04-26 8:16 ` Kashyap Chamarthy
2022-04-26 16:38 ` John Snow [this message]
2022-04-29 14:06 ` Beraldo Leal
2022-04-29 15:48 ` John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 05/12] add a couple new trove classifiers John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 06/12] move README.rst to FILES.rst and update John Snow
2022-04-25 13:23 ` Kashyap Chamarthy
2022-04-22 18:49 ` [qemu.qmp PATCH 07/12] move PACKAGE.rst to README.rst " John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 08/12] docs: add versioning policy to README John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 09/12] add LGPLv2+ and GPLv2 LICENSE files John Snow
2022-04-25 11:00 ` Daniel P. Berrangé
2022-04-22 18:49 ` [qemu.qmp PATCH 10/12] update Pipfile John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 11/12] remove sub-dependency pins from Pipfile John Snow
2022-04-25 13:19 ` Kashyap Chamarthy
2022-04-22 18:49 ` [qemu.qmp PATCH 12/12] update VERSION to 0.0.0a1 John Snow
2022-04-29 14:09 ` Beraldo Leal
2022-04-29 17:18 ` [qemu.qmp PATCH 00/12] python: fork qemu.qmp python lib into independent repo John Snow
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='CAFn=p-aFu0eHZCWT2acuiQLWeLVHt5gMyqc11TfiM0i3tqwMrA@mail.gmail.com' \
--to=jsnow@redhat.com \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=kchamart@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).