public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Proposal of accepting arguments to `default` in src_install (and more?) phases in EAPI=5 (for the next council meeting?)
Date: Sat, 12 May 2012 19:50:04 +0300	[thread overview]
Message-ID: <4FAE94BC.90106@gentoo.org> (raw)

Example,

- Package is using autotools.
- The default phase like below works for the package:

src_install() {
emake DESTDIR="${D}" install
dodoc README
}

So when writing a new ebuild you would only add:

DOCS="README"

And be done with it. Then the next version of the package needs extra 
argument passed to emake install, for example:

src_install() {
emake DESTDIR="${D}" init_d_path="/usr/share/doc/${PF}/examples" install
dodoc README
}

So you are /forced/ to write entire src_install() while you only want to 
append one argument to emake install.

The current workaround for this is to use EXTRA_EMAKE from ebuild, but I 
find this rather ugly (if not even forbidden by some PMS magic?)

Can we make econf in src_configure, emake in src_compile, and emake 
install in src_install accept arguments "$@" in EAPI=5, please?

Relavent bug is http://bugs.gentoo.org/364343

- Samuli



             reply	other threads:[~2012-05-12 16:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12 16:50 Samuli Suominen [this message]
2012-05-12 17:57 ` [gentoo-dev] Proposal of accepting arguments to `default` in src_install (and more?) phases in EAPI=5 (for the next council meeting?) Ulrich Mueller
2012-05-12 18:09   ` Michał Górny
2012-05-12 18:12     ` Samuli Suominen
2012-05-12 18:39     ` Ulrich Mueller
2012-05-14  4:58       ` [gentoo-dev] " Duncan
2012-05-14 14:05         ` Arfrever Frehtes Taifersar Arahesis
2012-05-12 18:42 ` [gentoo-dev] " julian
2012-05-12 18:43 ` hasufell

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=4FAE94BC.90106@gentoo.org \
    --to=ssuominen@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