public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Aaron Bauman" <bman@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: lxde-base/lxinput/
Date: Tue, 27 Mar 2018 00:45:21 +0000 (UTC)	[thread overview]
Message-ID: <1522111321.cf9dca4ad3baa59c18916ec2eb65b5924974f09f.bman@gentoo> (raw)

commit:     cf9dca4ad3baa59c18916ec2eb65b5924974f09f
Author:     charIes17 <charles17 <AT> arcor <DOT> de>
AuthorDate: Sun Jan 21 18:10:49 2018 +0000
Commit:     Aaron Bauman <bman <AT> gentoo <DOT> org>
CommitDate: Tue Mar 27 00:42:01 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cf9dca4a

lxde-base/lxinput: Remove old

  repo.eapi.deprecated          1
   lxde-base/lxinput/lxinput-0.3.2.ebuild: 4

Package-Manager: Portage-2.3.19, Repoman-2.3.6

 lxde-base/lxinput/Manifest             |  1 -
 lxde-base/lxinput/lxinput-0.3.2.ebuild | 20 --------------------
 2 files changed, 21 deletions(-)

diff --git a/lxde-base/lxinput/Manifest b/lxde-base/lxinput/Manifest
index 2e26457e069..e009690ad7f 100644
--- a/lxde-base/lxinput/Manifest
+++ b/lxde-base/lxinput/Manifest
@@ -1,2 +1 @@
-DIST lxinput-0.3.2.tar.gz 259203 BLAKE2B a6de344e5324cf745ee05e39c9211fb10a4fd1395bc295f08945192c9d833c2ddaa6007242e17db69cfcef1140ef6a932da8970c0e7cf39a2f6e0ac27fd2316e SHA512 50921151d3050fae1e4640aade2b0bf88d94445f95e18c21c3d67a012ec7d33b6b9dada8574898d915a350c37fcd568f376bafff1b804e222543a5cadf87431a
 DIST lxinput-0.3.5.tar.xz 145356 BLAKE2B e3c96a1232329afa5030adffc17af4adf9afc3eb1049f860fe6ed115eb35d580c24a69a21a9a858790b9213b7d4dc716ab9e30becf42b4f9645f2ec642de538c SHA512 d5233f03c4314ac16fb548db56ae2d17651b29d8a59bfef3e6e6805f6b9bc8100b0711bbc72e31a6bc458eccc6fe1b4a38cf097dbf6a1b04f600bba58ff03f35

diff --git a/lxde-base/lxinput/lxinput-0.3.2.ebuild b/lxde-base/lxinput/lxinput-0.3.2.ebuild
deleted file mode 100644
index 3d840aebb50..00000000000
--- a/lxde-base/lxinput/lxinput-0.3.2.ebuild
+++ /dev/null
@@ -1,20 +0,0 @@
-# Copyright 1999-2015 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI="4"
-
-DESCRIPTION="LXDE keyboard and mouse configuration tool"
-HOMEPAGE="http://lxde.sourceforge.net/"
-SRC_URI="mirror://sourceforge/lxde/${P}.tar.gz"
-
-LICENSE="GPL-2"
-SLOT="0"
-KEYWORDS="~alpha amd64 arm ~arm64 ppc x86 ~arm-linux ~x86-linux"
-IUSE=""
-
-RDEPEND="dev-libs/glib:2
-	x11-libs/gtk+:2"
-DEPEND="${RDEPEND}
-	sys-devel/gettext
-	virtual/pkgconfig
-	>=dev-util/intltool-0.40.0"


             reply	other threads:[~2018-03-27  0:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27  0:45 Aaron Bauman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-09  5:16 [gentoo-commits] repo/gentoo:master commit in: lxde-base/lxinput/ Sam James
2024-11-18 14:28 Sam James
2021-07-21 14:49 Yixun Lan
2021-03-15 13:14 Andreas Sturmlechner
2021-03-14  0:25 Andreas Sturmlechner
2021-03-05 22:20 Sam James
2020-05-11  6:55 Joonas Niilola
2018-07-10  4:58 Markus Meier
2018-06-23 18:33 Mikle Kolyada
2018-03-27  0:45 Aaron Bauman
2017-01-15 20:33 Markus Meier
2017-01-08 11:55 Aaron Bauman
2016-09-13 22:04 Hanno Boeck

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=1522111321.cf9dca4ad3baa59c18916ec2eb65b5924974f09f.bman@gentoo \
    --to=bman@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