From: "Tim Harder (radhermit)" <radhermit@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-lua/LuaBitOp: ChangeLog LuaBitOp-1.0.2.ebuild
Date: Thu, 30 Jan 2014 21:39:52 +0000 (UTC) [thread overview]
Message-ID: <20140130213952.1D58E2004C@flycatcher.gentoo.org> (raw)
radhermit 14/01/30 21:39:52
Modified: ChangeLog
Added: LuaBitOp-1.0.2.ebuild
Log:
Version bump (bug #499754).
(Portage version: 2.2.8-r1/cvs/Linux x86_64, signed Manifest commit with key 4AB3E85B4F064CA3)
Revision Changes Path
1.6 dev-lua/LuaBitOp/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-lua/LuaBitOp/ChangeLog?rev=1.6&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-lua/LuaBitOp/ChangeLog?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-lua/LuaBitOp/ChangeLog?r1=1.5&r2=1.6
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-lua/LuaBitOp/ChangeLog,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- ChangeLog 28 Aug 2011 11:24:59 -0000 1.5
+++ ChangeLog 30 Jan 2014 21:39:51 -0000 1.6
@@ -1,6 +1,11 @@
# ChangeLog for dev-lua/LuaBitOp
-# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-lua/LuaBitOp/ChangeLog,v 1.5 2011/08/28 11:24:59 hwoarang Exp $
+# Copyright 1999-2014 Gentoo Foundation; Distributed under the GPL v2
+# $Header: /var/cvsroot/gentoo-x86/dev-lua/LuaBitOp/ChangeLog,v 1.6 2014/01/30 21:39:51 radhermit Exp $
+
+*LuaBitOp-1.0.2 (30 Jan 2014)
+
+ 30 Jan 2014; Tim Harder <radhermit@gentoo.org> +LuaBitOp-1.0.2.ebuild:
+ Version bump (bug #499754).
28 Aug 2011; Markos Chandras <hwoarang@gentoo.org> LuaBitOp-1.0.1-r1.ebuild,
+files/LuaBitOp-ldflags.patch:
1.1 dev-lua/LuaBitOp/LuaBitOp-1.0.2.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-lua/LuaBitOp/LuaBitOp-1.0.2.ebuild?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-lua/LuaBitOp/LuaBitOp-1.0.2.ebuild?rev=1.1&content-type=text/plain
Index: LuaBitOp-1.0.2.ebuild
===================================================================
# Copyright 1999-2014 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/dev-lua/LuaBitOp/LuaBitOp-1.0.2.ebuild,v 1.1 2014/01/30 21:39:51 radhermit Exp $
EAPI="5"
inherit toolchain-funcs
DESCRIPTION="Bit Operations Library for the Lua Programming Language"
HOMEPAGE="http://bitop.luajit.org"
SRC_URI="http://bitop.luajit.org/download/${P}.tar.gz"
LICENSE="MIT"
SLOT="0"
KEYWORDS="~amd64 ~x86"
IUSE=""
RDEPEND="dev-lang/lua"
DEPEND="${RDEPEND}
virtual/pkgconfig"
src_compile()
{
emake CC="$(tc-getCC)" INCLUDES= CCOPT=
}
src_install()
{
exeinto "$(pkg-config --variable INSTALL_CMOD lua)"
doexe bit.so
dodoc README
dohtml -r doc/*
}
next reply other threads:[~2014-01-30 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 21:39 Tim Harder (radhermit) [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-22 17:41 [gentoo-commits] gentoo-x86 commit in dev-lua/LuaBitOp: ChangeLog LuaBitOp-1.0.2.ebuild Jeroen Roovers (jer)
2014-02-25 20:50 Markus Meier (maekke)
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=20140130213952.1D58E2004C@flycatcher.gentoo.org \
--to=radhermit@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