From: "Mart Raudsepp (leio)" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in sys-devel/libtool: ChangeLog libtool-1.3.5.ebuild
Date: Sun, 6 Feb 2011 11:36:46 +0000 (UTC) [thread overview]
Message-ID: <20110206113646.4CC9C20054@flycatcher.gentoo.org> (raw)
leio 11/02/06 11:36:46
Modified: ChangeLog libtool-1.3.5.ebuild
Log:
Drop to ~mips
(Portage version: 2.1.9.35/cvs/Linux mips64)
Revision Changes Path
1.183 sys-devel/libtool/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-devel/libtool/ChangeLog?rev=1.183&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-devel/libtool/ChangeLog?rev=1.183&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-devel/libtool/ChangeLog?r1=1.182&r2=1.183
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sys-devel/libtool/ChangeLog,v
retrieving revision 1.182
retrieving revision 1.183
diff -u -r1.182 -r1.183
--- ChangeLog 29 Nov 2010 15:12:34 -0000 1.182
+++ ChangeLog 6 Feb 2011 11:36:46 -0000 1.183
@@ -1,6 +1,9 @@
# ChangeLog for sys-devel/libtool
-# Copyright 1999-2010 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/sys-devel/libtool/ChangeLog,v 1.182 2010/11/29 15:12:34 flameeyes Exp $
+# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
+# $Header: /var/cvsroot/gentoo-x86/sys-devel/libtool/ChangeLog,v 1.183 2011/02/06 11:36:46 leio Exp $
+
+ 06 Feb 2011; Mart Raudsepp <leio@gentoo.org> libtool-1.3.5.ebuild:
+ Drop to ~mips
*libtool-2.4-r1 (29 Nov 2010)
1.9 sys-devel/libtool/libtool-1.3.5.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-devel/libtool/libtool-1.3.5.ebuild?rev=1.9&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-devel/libtool/libtool-1.3.5.ebuild?rev=1.9&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-devel/libtool/libtool-1.3.5.ebuild?r1=1.8&r2=1.9
Index: libtool-1.3.5.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sys-devel/libtool/libtool-1.3.5.ebuild,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- libtool-1.3.5.ebuild 22 Apr 2008 23:02:32 -0000 1.8
+++ libtool-1.3.5.ebuild 6 Feb 2011 11:36:46 -0000 1.9
@@ -1,6 +1,6 @@
-# Copyright 1999-2008 Gentoo Foundation
+# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/sys-devel/libtool/libtool-1.3.5.ebuild,v 1.8 2008/04/22 23:02:32 vapier Exp ${P}-r1.ebuild,v 1.8 2002/10/04 06:34:42 kloeri Exp $
+# $Header: /var/cvsroot/gentoo-x86/sys-devel/libtool/libtool-1.3.5.ebuild,v 1.9 2011/02/06 11:36:46 leio Exp ${P}-r1.ebuild,v 1.8 2002/10/04 06:34:42 kloeri Exp $
DESCRIPTION="A shared library tool for developers"
HOMEPAGE="http://www.gnu.org/software/libtool/"
@@ -8,7 +8,7 @@
LICENSE="GPL-2"
SLOT="1.3"
-KEYWORDS="alpha amd64 arm hppa ia64 m68k mips ppc ppc64 s390 sh sparc x86"
+KEYWORDS="alpha amd64 arm hppa ia64 m68k ~mips ppc ppc64 s390 sh sparc x86"
IUSE=""
src_compile() {
reply other threads:[~2011-02-06 11:36 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=20110206113646.4CC9C20054@flycatcher.gentoo.org \
--to=leio@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