public inbox for gentoo-devhelp@lists.gentoo.org
 help / color / mirror / Atom feed
From: waltdnes@waltdnes.org
To: Gentoo Devhelp <gentoo-devhelp@lists.gentoo.org>
Subject: [gentoo-devhelp] Git and ebuild interaction
Date: Sat, 11 Jun 2016 13:58:57 -0400	[thread overview]
Message-ID: <20160611175857.GA15365@waltdnes.org> (raw)

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

  I'm proposing a new eselect module to control cpu frequency scaling
at https://bugs.gentoo.org/show_bug.cgi?id=584814  IANAD (I Am Not A
Developer).  Bash scripting is my main talent, and that's what eselect
modules happen to consist of.  I've got the module uploaded to...
https://github.com/walterdnes/cpugov/blob/master/cpugov.eselect and a
revised ebuild (as per comment 15 in the bug) is attached to the email.

  I can't get any further because I can't download the file via the
ebuild, to generate a manifest and a digest.  What should I upload on
the git site?  Should it be a compressed file cpugov.eselect-0.1.tar?
And what are the exact instructions for that?

  A separate question... where can I find a centralized list of ebuild
functions like insinto and doins?

-- 
Walter Dnes <waltdnes@waltdnes.org>

[-- Attachment #2: eselect-cpugov-0.1.ebuild --]
[-- Type: text/plain, Size: 432 bytes --]

# Copyright 2016 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Id$

EAPI=6

DESCRIPTION="Manages cpu governor and frequency selection"
HOMEPAGE="https://www.gentoo.org/No_homepage"
SRC_URI="https://github.com/walterdnes/${P}"

LICENSE="GPL-2+"
SLOT="0"
KEYWORDS="~amd64 ~x86"
IUSE=""

RDEPEND="app-admin/eselect"

src_install() {
	insinto /usr/share/eselect/modules
	doins cpugov.eselect
}

                 reply	other threads:[~2016-06-11 17:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160611175857.GA15365@waltdnes.org \
    --to=waltdnes@waltdnes.org \
    --cc=gentoo-devhelp@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