public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: yngwin@gmail.com
Subject: Re: [gentoo-dev] RFC: an eclass for github snapshots?
Date: Mon, 19 Mar 2012 09:41:46 +0100	[thread overview]
Message-ID: <20120319094146.2b58617e@pomiocik.lan> (raw)
In-Reply-To: <20120312104741.4d2daaaf@pomiocik.lan>

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

On Mon, 12 Mar 2012 10:47:41 +0100
Michał Górny <mgorny@gentoo.org> wrote:

> On Mon, 12 Mar 2012 09:36:00 +0800
> Ben <yngwin@gmail.com> wrote:
> 
> > On 12 March 2012 02:27, Michał Górny <mgorny@gentoo.org> wrote:
> > > On Sun, 11 Mar 2012 10:25:38 -0700 (PDT)
> > > Leho Kraav <leho@kraav.com> wrote:
> > >
> > >> On Monday, May 30, 2011 9:30:02 AM UTC+3, Michał Górny wrote:
> > >> >
> > >> > Right now, a quick 'grep -l github.*tarball' shows that there
> > >> > are about 147 ebuilds in portage using github snapshots. This
> > >> > evaluates to 83 different packages.
> > >> >
> > >> > The problem with github is that it suffixes the tarballs with
> > >> > a complete git commit id. This means that the `S' variable
> > >> > in the ebuild needs to refer to a long hash changing randomly.
> > >> > Right now, the problem is handled in a number of ways:
> > >> >
> > >> > 1) (from app-admin/rudy)
> > >> > 2) (app-emacs/calfw and suggested solution for Sunrise)
> > >> > 3) (app-misc/bgrep)
> > >> > 4) (app-misc/tmux-mem-cpu-load)
> > >> >
> > >> > What I'd like to do is creating a small github.eclass,
> > >> > encapsulating a common, nice way of handling the S issue. I
> > >> > guess the best solution would be to git with something like 2)
> > >> > above, with the eclass providing github_src_unpack() for EAPIs
> > >> > 2+.
> > >>
> > >> What is the current situation with this one? Every once in a
> > >> while I run into a github ebuild I need to create and I am not
> > >> really sure what to do with it.
> > >>
> > >> Right now 2) seems like the safest approach. But did anything get
> > >> into EAPI?
> > >
> > > You mean eclass? I submitted one for review but didn't get much of
> > > positive feedback on it. I'll commit it anyway soon, just let me
> > > double check and do some testing.
> > 
> > +1 from me. I think it would be useful to have a standard way of
> > handling this.
> 
> Attaching my current conceptual eclass. I've tested it with github,
> gitweb and bitbucket. It won't work with gitorious but their snapshot
> download mechanism is broken anyway (they like to submit 'try again
> later' in plaintext).

Committed.

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  reply	other threads:[~2012-03-19  8:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gY49c-206-11@gated-at.bofh.it>
2012-03-11 17:25 ` [gentoo-dev] RFC: an eclass for github snapshots? Leho Kraav
2012-03-11 18:15   ` Zac Medico
2012-03-11 18:27   ` Michał Górny
2012-03-12  1:36     ` Ben
2012-03-12  9:47       ` Michał Górny
2012-03-19  8:41         ` Michał Górny [this message]
2011-05-30  6:27 Michał Górny

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=20120319094146.2b58617e@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=yngwin@gmail.com \
    /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