From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:pkg-config commit in: /
Date: Thu, 29 Nov 2012 21:06:00 +0000 (UTC) [thread overview]
Message-ID: <1353940564.1e6b805919ca7647b7c4aa7265a093e62d542eb1.jlec@gentoo> (raw)
commit: 1e6b805919ca7647b7c4aa7265a093e62d542eb1
Author: Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 26 14:36:04 2012 +0000
Commit: Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Mon Nov 26 14:36:04 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/sci.git;a=commit;h=1e6b8059
* cuda:
dev-util/nvidia-cuda-sdk: Version Bump, inclusive cuda.eclass usage
sci-chemistry/vmd: Using new cuda.eclass
Imported from tree
Preparing Version Bump
dev-util/nvidia-cuda-toolkit: Merge change in both versions; fix whitespace error
Correcting whitespace problem
Minor fixes
Be a little more informative.
do not call pkg_setup from cuda.eclass
Move pkg_postinst to dev-util/nvidia-cuda-toolkit
Adding ignores for Mac
Add comments and streamline
dev-util/nvidia-cuda-sdk: Preparing Version Bump
Add pkg_setup and gcc bindir detection
dev-util/nvidia-cuda-toolkit: Enhancing cuda-config
dev-util/nvidia-cuda-sdk: Reverted changes to bicatalis commit; Moving to cuda.eclass
dev-util/nvidia-cuda-toolkit: Version Bump
preliminary cuda.eclass
Work in progress towards cuda eclass usage
dev-util/nvidia-cuda-toolkit: Use cuda.eclass; install cuda-config; install doc and html into system path to support portages file filter
.gitignore | 1 -
dev-util/nvidia-cuda-sdk/ChangeLog | 15 +
dev-util/nvidia-cuda-sdk/Manifest | 2 +
.../files/nvidia-cuda-sdk-5.0.35-asneeded.patch | 4159 ++++++++++++++++++++
dev-util/nvidia-cuda-sdk/metadata.xml | 13 +-
.../nvidia-cuda-sdk-4.2.9-r1.ebuild | 112 +
.../nvidia-cuda-sdk/nvidia-cuda-sdk-4.2.9.ebuild | 69 -
.../nvidia-cuda-sdk/nvidia-cuda-sdk-5.0.35.ebuild | 119 +
dev-util/nvidia-cuda-toolkit/ChangeLog | 20 +
dev-util/nvidia-cuda-toolkit/Manifest | 6 +-
dev-util/nvidia-cuda-toolkit/files/cuda-config.in | 28 +
dev-util/nvidia-cuda-toolkit/metadata.xml | 13 +-
.../nvidia-cuda-toolkit-4.2.9-r1.ebuild | 106 +
.../nvidia-cuda-toolkit-4.2.9.ebuild | 73 -
.../nvidia-cuda-toolkit-5.0.35.ebuild | 111 +
eclass/cuda.eclass | 123 +
sci-chemistry/vmd/ChangeLog | 238 ++
sci-chemistry/vmd/Manifest | 2 +
sci-chemistry/vmd/metadata.xml | 15 +
sci-chemistry/vmd/vmd-1.9.1-r1.ebuild | 223 ++
20 files changed, 5290 insertions(+), 158 deletions(-)
next reply other threads:[~2012-11-29 21:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 21:06 Justin Lecher [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-29 21:06 [gentoo-commits] proj/sci:pkg-config commit in: / Justin Lecher
2012-11-29 21:06 Justin Lecher
2012-11-29 21:06 Justin Lecher
2012-11-29 21:06 Justin Lecher
2012-11-29 21:06 Justin Lecher
2012-11-29 21:05 Justin Lecher
2012-11-29 21:05 Justin Lecher
2012-11-29 21:05 Justin Lecher
2012-11-29 21:05 Justin Lecher
2012-11-29 21:05 Justin Lecher
2012-11-29 7:03 [gentoo-commits] proj/sci:master " Justin Lecher
2012-11-29 21:06 ` [gentoo-commits] proj/sci:pkg-config " Justin Lecher
2012-11-26 22:02 [gentoo-commits] proj/sci:master " Justin Lecher
2012-11-29 21:06 ` [gentoo-commits] proj/sci:pkg-config " Justin Lecher
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=1353940564.1e6b805919ca7647b7c4aa7265a093e62d542eb1.jlec@gentoo \
--to=jlec@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