public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Auty <ikelos@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] How to deal with git sources?
Date: Sun, 11 Mar 2018 18:05:04 +0000	[thread overview]
Message-ID: <4d372700-be86-bffa-408c-d923caa2edd5@gentoo.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 750 bytes --]

Hiya,

I'm trying to update/package up mypy for the main tree which, whilst it
provides a release tarball, relies upon a data library (typeshed) which
does not provide releases.  The recommended method of installation by
upstream is to use git submodules (which the ebuild will do happily),
but repoman rightly complains about LIVEVCS issues.

Is the current recommended method for dealing with this to manually
create a tarball and stash it on dev.gentoo.org somewhere accessible or
are there updated guidelines for this kind of scenario?  If so, where
would they be documented?  Searching for LIVECVS found a bunch of
repoman change discussions, but no documentation as to how to deal with
ebuilds that require this...

Mike  5:)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 368 bytes --]

             reply	other threads:[~2018-03-11 18:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-11 18:05 Mike Auty [this message]
2018-03-11 19:19 ` [gentoo-dev] How to deal with git sources? Mike Auty
2018-03-12  4:30   ` [gentoo-dev] " Duncan
2018-03-12  8:29     ` Martin Vaeth
2018-03-12 13:20       ` Michael Orlitzky
2018-03-13 13:33         ` Martin Vaeth
2018-03-15 16:48           ` Vadim A. Misbakh-Soloviov
2018-03-15 23:20             ` Martin Vaeth
2018-03-16  4:03               ` NP-Hardass
2018-03-16  9:28                 ` Martin Vaeth
2018-03-16  7:19               ` Ulrich Mueller
2018-03-16  7:27                 ` Ulrich Mueller
2018-03-16 10:03                 ` Martin Vaeth
2018-03-16 10:17                   ` James Le Cuirot
2018-03-16 11:00                   ` Ulrich Mueller
2018-03-16 11:04                     ` Michał Górny
2018-03-16 17:21                     ` William Hubbs
2018-03-16 17:34                       ` Rich Freeman

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=4d372700-be86-bffa-408c-d923caa2edd5@gentoo.org \
    --to=ikelos@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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