From: "Rafael Martins (rafaelmartins)" <rafaelmartins@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in app-portage/g-octave: ChangeLog g-octave-0.4.1.ebuild
Date: Sun, 24 Oct 2010 01:19:50 +0000 (UTC) [thread overview]
Message-ID: <20101024011950.63DCD20051@flycatcher.gentoo.org> (raw)
rafaelmartins 10/10/24 01:19:50
Modified: ChangeLog g-octave-0.4.1.ebuild
Log:
Fixed pkg_config phase.
(Portage version: 2.2.0_alpha1/cvs/Linux x86_64)
Revision Changes Path
1.3 app-portage/g-octave/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-portage/g-octave/ChangeLog?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-portage/g-octave/ChangeLog?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-portage/g-octave/ChangeLog?r1=1.2&r2=1.3
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/app-portage/g-octave/ChangeLog,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ChangeLog 24 Oct 2010 01:06:00 -0000 1.2
+++ ChangeLog 24 Oct 2010 01:19:50 -0000 1.3
@@ -1,6 +1,10 @@
# ChangeLog for app-portage/g-octave
# Copyright 1999-2010 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/app-portage/g-octave/ChangeLog,v 1.2 2010/10/24 01:06:00 rafaelmartins Exp $
+# $Header: /var/cvsroot/gentoo-x86/app-portage/g-octave/ChangeLog,v 1.3 2010/10/24 01:19:50 rafaelmartins Exp $
+
+ 24 Oct 2010; Rafael G. Martins <rafaelmartins@gentoo.org>
+ g-octave-0.4.1.ebuild:
+ Fixed pkg_config phase.
*g-octave-0.4.1 (24 Oct 2010)
1.2 app-portage/g-octave/g-octave-0.4.1.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-portage/g-octave/g-octave-0.4.1.ebuild?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-portage/g-octave/g-octave-0.4.1.ebuild?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-portage/g-octave/g-octave-0.4.1.ebuild?r1=1.1&r2=1.2
Index: g-octave-0.4.1.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/app-portage/g-octave/g-octave-0.4.1.ebuild,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- g-octave-0.4.1.ebuild 24 Oct 2010 01:06:00 -0000 1.1
+++ g-octave-0.4.1.ebuild 24 Oct 2010 01:19:50 -0000 1.2
@@ -1,6 +1,6 @@
# Copyright 1999-2010 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/app-portage/g-octave/g-octave-0.4.1.ebuild,v 1.1 2010/10/24 01:06:00 rafaelmartins Exp $
+# $Header: /var/cvsroot/gentoo-x86/app-portage/g-octave/g-octave-0.4.1.ebuild,v 1.2 2010/10/24 01:19:50 rafaelmartins Exp $
EAPI="2"
SUPPORT_PYTHON_ABIS="1"
@@ -77,7 +77,7 @@
local db="$(g-octave --config db)"
mkdir -p "${db}"
einfo "Extracting g-octave database files to: ${db}"
- tar -xzf "${DISTDIR}/${PF}-db.tar.gz" -C "${db}" || die 'tar failed.'
+ tar -xzf "${DISTDIR}/${PN}-db-${DB_COMMIT:0:7}.tar.gz" -C "${db}" || die 'tar failed.'
rm -rf "${db}"/{patches,octave-forge,info.json,timestamp}
mv -f "${db}/${DB_DIR}"/* "${db}" || die 'mv failed.'
rm -rf "${db}/${DB_DIR}"
reply other threads:[~2010-10-24 1:19 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=20101024011950.63DCD20051@flycatcher.gentoo.org \
--to=rafaelmartins@gentoo.org \
--cc=gentoo-commits@lists.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