public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [discussion] GitHub eclass
Date: Fri, 22 Feb 2013 20:37:40 +1300	[thread overview]
Message-ID: <CAATnKFCddfu9J+V2PqUjMW=ZOhjf9NMRGhNH8=5Y4Zv-Hc8EKg@mail.gmail.com> (raw)
In-Reply-To: <512715FA.5050800@mva.name>

On 22 February 2013 19:53, Vadim A. Misbakh-Soloviov <mva@mva.name> wrote:
> Hi there!
>
> Since we have tons of ebuild (including -9999) for software, that uses
> GitHub for sourcecode hosting —  I've got an idea to write something
> like GitHub eclass, which will ease creating of such ebuilds (by
> providing "sugar" functions) and, (main goal for me) by adding
> possibility to switch between forks (by redefining variables on emerge
> run). For example (theoretical usecase):
>
> We have, for example, lua-socket-9999, that uses:
> GH_AUTHOR=diegonehab
> GH_PROJECT=lua-socket
> GH_BRANCH=unstable
>
> So, then I fork it and provide some features. And then I want to
> reemerge it from my fork, but I don't want to rewrite ebuild. So, then I do:
> # GH_AUTHOR="msva" GH_BRANCH=master emerge =lua-socket-9999
> and it repulls sources from my fork, reemerge it and installs fine.

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

-- 
Kent


  reply	other threads:[~2013-02-22  7:37 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 [this message]
2013-02-22  7:43   ` Diego Elio Pettenò
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='CAATnKFCddfu9J+V2PqUjMW=ZOhjf9NMRGhNH8=5Y4Zv-Hc8EKg@mail.gmail.com' \
    --to=kentfredric@gmail.com \
    --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