public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org, pva@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in net-firewall/ipset: ChangeLog metadata.xml ipset-2.3.0.20070828.ebuild
Date: Mon, 5 Nov 2007 10:03:21 -0800	[thread overview]
Message-ID: <20071105180321.GF25343@supernova> (raw)
In-Reply-To: <E1Ip2rU-0003os-Bw@stork.gentoo.org>

On 14:23 Mon 05 Nov     , Peter Volkov (pva) wrote:
> 1.1                  net-firewall/ipset/ipset-2.3.0.20070828.ebuild
> 
> file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-firewall/ipset/ipset-2.3.0.20070828.ebuild?rev=1.1&view=markup
> plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-firewall/ipset/ipset-2.3.0.20070828.ebuild?rev=1.1&content-type=text/plain

> src_defs() {
> 	# these are used in both of src_compile and src_install
> 	myconf="${myconf} PREFIX="
> 	myconf="${myconf} LIBDIR=/lib"

Should this be get_libdir()?

Also seems like instead of having a function to do this, you could just 
define the variables once in pkg_setup() or src_compile() as globals.

> pkg_config() {
> 	cd "${ROOT}${PORTAGE_TMPDIR}"
> 	mkdir patch-o-matic-ng
> 	cd patch-o-matic-ng
> 
> 	IPTVERINS=`echo $(best_version net-firewall/iptables) | \
> 	sed -n 's:^[^/]*/[[:alpha:]]*-\([0-9]\+\([.][0-9]\+\)*[a-z]\?\(_\(pre\|p\|beta\|alpha\|rc\)[0-9]*\)*\)\(-r[0-9]\+\)\?$:\1:p'`
> 
> 	einfo "Unpacking patch-o-matic-ng-${POM_PV}"
> 	tar -jxf "${DISTDIR}"/patch-o-matic-ng-${POM_PV}.tar.bz2 || \
> 				die "Unable to unpack patch-o-matic-ng-${POM_PV}"
> 	einfo "Unpacking iptables-${IPTVERINS}"
> 	tar -jxf "${DISTDIR}"/iptables-${IPTVERINS}.tar.bz2 || \
> 				die "Unable to unpack iptables-${IPTVERINS}.tar.bz2"

Could you just call unpack() here?

> 	einfo "Enter path to your kernel sources, relative to ${ROOT}"
> 	echo -n "[/usr/src/linux]: "
> 	read K_DIR
> 	[ "${ROOT}${K_DIR}" == "/" ] && K_DIR=${ROOT}/usr/src/linux

/usr/src/linux should be what's used here, and if they want to change 
the kernel to affect, they should change where the symlink points 
instead of having a secondary config mechanism.

Thanks,
Donnie
-- 
gentoo-dev@gentoo.org mailing list



       reply	other threads:[~2007-11-05 18:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Ip2rU-0003os-Bw@stork.gentoo.org>
2007-11-05 18:03 ` Donnie Berkholz [this message]
2007-11-07  9:06   ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in net-firewall/ipset: ChangeLog metadata.xml ipset-2.3.0.20070828.ebuild Peter Volkov
2007-11-07 23:19     ` Donnie Berkholz
2007-11-08  2:04       ` Alec Warner

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=20071105180321.GF25343@supernova \
    --to=dberkholz@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=pva@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