From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-laptop/hdaps-gl/
Date: Fri, 22 Nov 2019 13:06:30 +0000 (UTC) [thread overview]
Message-ID: <1574427807.a38f4333df739bdf75bcb81bfd33c373f1b71612.mjo@gentoo> (raw)
commit: a38f4333df739bdf75bcb81bfd33c373f1b71612
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Fri Nov 22 12:46:09 2019 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Fri Nov 22 13:03:27 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a38f4333
app-laptop/hdaps-gl: Revert "[QA] expand HOMAPAGE in SRC_URI"
Putting the "[QA]" tag at the beginning of your commit message doesn't
give you any special powers to change things unrelated to published QA
policies.
This package was unmaintained, EAPI=4, and package.masked. To clean it
up, I...
* Took over as maintainer.
* Unmasked it.
* Made a new EAPI=7 revision.
* Contacted upstream about moving the project to github.
* Formed a new github organization, linux-thinkpad, to consolidate
hdaps, tp_smapi, and hdaps-gl development.
* Forked the SourceForge repository.
* Found a license issue that no one was aware of, and dug through
hundreds of mailing list posts to track down everyone with a
copyright claim to the code.
* Emailed all of those people, and waited to hear back so that
we can be reasonably sure that this code is actually GPL-2.
* Gave the project a real autotools build system (fixing a linking bug).
* Updated the code to display a better error message when you're missing
the hardware.
* Merged some other Github contributions that people made while the
project was "dead."
* Made an official v0.0.7 release on Github.
* Added v0.0.7 to Gentoo, eliminating the need for all non-default phase
functions and the patch that we've been carrying around.
* Fixed some missing (linked) dependencies in the ebuild in the process.
And you want to make this sort of thing even *more* work, by fighting
over whether SRC_URI fits on an 80 character line or contains a
variable? When there's no QA policy about it either way? Just no.
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
app-laptop/hdaps-gl/hdaps-gl-0.0.7.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/app-laptop/hdaps-gl/hdaps-gl-0.0.7.ebuild b/app-laptop/hdaps-gl/hdaps-gl-0.0.7.ebuild
index bc461ec98a6..3fafe3240d2 100644
--- a/app-laptop/hdaps-gl/hdaps-gl-0.0.7.ebuild
+++ b/app-laptop/hdaps-gl/hdaps-gl-0.0.7.ebuild
@@ -4,8 +4,8 @@
EAPI=7
DESCRIPTION="OpenGL visualization for HDAPS data"
-HOMEPAGE="https://github.com/linux-thinkpad/hdaps-gl"
-SRC_URI="https://github.com/linux-thinkpad/hdaps-gl/releases/download/${PV}/${P}.tar.xz"
+HOMEPAGE="https://github.com/linux-thinkpad/${PN}"
+SRC_URI="${HOMEPAGE}/releases/download/${PV}/${P}.tar.xz"
LICENSE="GPL-2"
SLOT="0"
next reply other threads:[~2019-11-22 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 13:06 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-31 16:54 [gentoo-commits] repo/gentoo:master commit in: app-laptop/hdaps-gl/ Michael Orlitzky
2019-12-19 22:07 Michael Orlitzky
2019-11-23 2:12 Aaron Bauman
2019-11-22 12:01 Mikle Kolyada
2019-11-22 0:55 Michael Orlitzky
2019-11-10 13:26 Michael Orlitzky
2019-11-10 13:26 Michael Orlitzky
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=1574427807.a38f4333df739bdf75bcb81bfd33c373f1b71612.mjo@gentoo \
--to=mjo@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