From: "Andreas Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/kde:master commit in: kde-base/korundum/
Date: Mon, 5 Aug 2013 18:51:57 +0000 (UTC) [thread overview]
Message-ID: <1375728538.4713de35e3e7bddd18cbaed7bc02eb4762c08af1.dilfridge@gentoo> (raw)
commit: 4713de35e3e7bddd18cbaed7bc02eb4762c08af1
Author: Andreas K. Huettel (dilfridge) <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 5 18:48:58 2013 +0000
Commit: Andreas Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Mon Aug 5 18:48:58 2013 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=commit;h=4713de35
[kde-base/korundum] update HOMEPAGE, bug 479252
Package-Manager: portage-2.2.0_alpha191
---
kde-base/korundum/korundum-4.10.97.ebuild | 1 +
kde-base/korundum/korundum-4.11.49.9999.ebuild | 1 +
kde-base/korundum/korundum-9999.ebuild | 1 +
3 files changed, 3 insertions(+)
diff --git a/kde-base/korundum/korundum-4.10.97.ebuild b/kde-base/korundum/korundum-4.10.97.ebuild
index b8dff31..c1212d0 100644
--- a/kde-base/korundum/korundum-4.10.97.ebuild
+++ b/kde-base/korundum/korundum-4.10.97.ebuild
@@ -17,6 +17,7 @@ inherit kde4-base ruby-ng
DESCRIPTION="KDE Ruby bindings"
KEYWORDS=" ~amd64 ~x86 ~amd64-linux ~x86-linux"
IUSE="akonadi debug kate okular"
+HOMEPAGE="http://techbase.kde.org/Development/Languages/Ruby"
# unfortunately single modules cannot be disabled with cmake defines
# possible more useflags have no effect... does anyone actually build this stuff?
diff --git a/kde-base/korundum/korundum-4.11.49.9999.ebuild b/kde-base/korundum/korundum-4.11.49.9999.ebuild
index 8069d4d..4b40844 100644
--- a/kde-base/korundum/korundum-4.11.49.9999.ebuild
+++ b/kde-base/korundum/korundum-4.11.49.9999.ebuild
@@ -17,6 +17,7 @@ inherit kde4-base ruby-ng
DESCRIPTION="KDE Ruby bindings"
KEYWORDS=""
IUSE="akonadi debug kate okular"
+HOMEPAGE="http://techbase.kde.org/Development/Languages/Ruby"
# unfortunately single modules cannot be disabled with cmake defines
# possible more useflags have no effect... does anyone actually build this stuff?
diff --git a/kde-base/korundum/korundum-9999.ebuild b/kde-base/korundum/korundum-9999.ebuild
index 8069d4d..4b40844 100644
--- a/kde-base/korundum/korundum-9999.ebuild
+++ b/kde-base/korundum/korundum-9999.ebuild
@@ -17,6 +17,7 @@ inherit kde4-base ruby-ng
DESCRIPTION="KDE Ruby bindings"
KEYWORDS=""
IUSE="akonadi debug kate okular"
+HOMEPAGE="http://techbase.kde.org/Development/Languages/Ruby"
# unfortunately single modules cannot be disabled with cmake defines
# possible more useflags have no effect... does anyone actually build this stuff?
next reply other threads:[~2013-08-05 18:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 18:51 Andreas Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-07 22:26 [gentoo-commits] proj/kde:master commit in: kde-base/korundum/ Johannes Huber
2015-08-07 22:24 Johannes Huber
2014-12-02 13:10 Manuel Rüger
2014-05-05 12:44 Johannes Huber
2014-05-04 23:35 Johannes Huber
2013-10-06 19:57 Chris Reffett
2013-07-04 18:05 Johannes Huber
2013-07-03 19:20 Michael Palimaka
2013-06-21 10:39 Johannes Huber
2012-04-13 21:51 Johannes Huber
2011-12-27 21:38 Andreas Hüttel
2011-09-07 21:43 Alexey Shvetsov
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=1375728538.4713de35e3e7bddd18cbaed7bc02eb4762c08af1.dilfridge@gentoo \
--to=dilfridge@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