From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [discussion] GitHub eclass
Date: Fri, 22 Feb 2013 08:43:05 +0100 [thread overview]
Message-ID: <51272189.6020505@flameeyes.eu> (raw)
In-Reply-To: <CAATnKFCddfu9J+V2PqUjMW=ZOhjf9NMRGhNH8=5Y4Zv-Hc8EKg@mail.gmail.com>
On 22/02/2013 08:37, Kent Fredric wrote:
> I'd make sure to add some sort of easy support to switch to
> snapshotted tar.gz installs instead of live git checkouts, ie:
>
> GH_SNAPSHOT=deadbeef # use commit id 'deadbeef' by fetching a tar.gz
> from github instead of a git clone
This is not going to fly because a live git checkout does not need
digests in the manifest, but a tar.gz snapshot does.
I'm not against having a common way to deal with github project as they
are common, but just having a wrapper for a few variables is not worth
it IMHO.
--
Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/
next prev parent reply other threads:[~2013-02-22 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 6:53 [gentoo-dev] [discussion] GitHub eclass Vadim A. Misbakh-Soloviov
2013-02-22 7:37 ` Kent Fredric
2013-02-22 7:43 ` Diego Elio Pettenò [this message]
2013-02-22 9:51 ` Kent Fredric
2013-02-22 13:49 ` Ian Stakenvicius
2013-02-22 14:00 ` Michał Górny
2013-02-22 15:09 ` Rich Freeman
2013-02-22 16:19 ` [gentoo-dev] " Duncan
2013-02-22 16:30 ` Ian Stakenvicius
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=51272189.6020505@flameeyes.eu \
--to=flameeyes@flameeyes.eu \
--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