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@gentoo.org>
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"